| Issue 67: | Changes should defer merging until merge commits are ready | |
| 4 people starred this issue and may be notified of changes. | Back to list |
Reported by Shawn Pearce <sop@google.com> on Mon Feb 09 10:41:31 PST 2009 Source: JIRA GERRIT-67 Affected Version: 2.0.3 If a change is an ancestor of a merge commit and the change is submitted into the branch's submit queue we should prevent it from merging immediately and try to wait for the merge commit to enter the submit queue too. If a merge commit exists its likely the merge wasn't path clean, so we need the merge commit anyway to get the change into the branch. But even if the merge is path clean if a merge commit exists the author may have explicitly created it, in which case they would prefer to have their own merge commit used rather than a system generated one.
Sep 28, 2009
Partially addressed by Ibe66d7c844141ae101a0e145f201232d0fc91f4d. In Ibe66d7 we wait 15 minutes to report a missing dependency. This makes it slightly cleaner to start at the tip of a chain of commits and walk backwards, submitting each change before its ancestor is submitted. If you can get all of them submitted in under 15 minutes, no "missing dependency" errors are sent. Unfortunately this still doesn't address the other direction, which is what the issue is talking about in its description, so I'm leaving it open until that is also dealt with.
Labels:
FixedIn-2.0.22
Sep 28, 2009
(No comment was entered for this change.)
Owner:
s...@google.com
Sep 28, 2009
(No comment was entered for this change.)
Status:
Started
Nov 21, 2009
(No comment was entered for this change.)
Owner:
s...@google.com
|
|
| ► Sign in to add a comment |
Owner: ---