************************************************************
***** NOTE: THIS BUG TRACKER IS FOR GERRIT CODE REVIEW *****
***** DO NOT SUBMIT BUGS FOR CHROME, ANDROID, INTERNAL *****
***** ISSUES WITH YOUR COMPANY'S GERRIT SETUP, ETC. *****
***** THOSE ISSUE BELONG IN DIFFERENT ISSUE TRACKERS! *****
************************************************************
Affected Version:
2.4.1
What steps will reproduce the problem?
1. Create projects "super", "sub1" and "sub2"
2. Add "sub1" as a submodule of "super" and ensure submodule_subscription is created.
3. Add "sub2" as a submodule of "sub1" and ensure submodule_subscription is created.
Now you have
Super
+---sub1
+-----sub2
4. Submit a change to sub2
What is the expected output?
"sub1" should get a new commit reflecting the new tip gitlink in sub2.
"super" should get a new commit reflecting that new tip gitlink in sub1 which was created by the submit into sub2.
What do you see instead?
"sub1" gets a new commit reflecting the new tip gitlink in sub2, but "super" is not updated.
Please provide any additional information below.
This is a recursive submodule arrangement, in case I was not clear.
Mergedinto: 1491