Currently, git-drover gives up and cleans up if the cherry-pick fails.
This change allows the user to manually resolve conflicts when using
git-drover.
BUG=404755
Review URL: https://codereview.chromium.org/1397313002
git-svn-id: svn://svn.chromium.org/chrome/trunk/tools/depot_tools@297429 0039d316-1c4b-4281-b951-d872f2087c98
<divclass="paragraph"><p><code>git drover</code> applies a commit to a release branch. It creates a new workdir from
an existing checkout to avoid downloading a new checkout without affecting the
existing checkout. Creating a workdir requires symlinks so this does not work on
Windows. See the EXAMPLE section for the equivalent sequence of commands to run.</p></div>
existing checkout.</p></div>
<divclass="paragraph"><p><code>git drover</code> does not support reverts. See the EXAMPLE section for the
equivalent sequence of commands to run.</p></div>
</div>
@ -794,6 +795,25 @@ equivalent sequence of commands to run.</p></div>
</p>
</dd>
<dtclass="hdlist1">
--continue [path_to_workdir]
</dt>
<dd>
<p>
Continue a cherry-pick that required manual resolution. The path to the drover
workdir is optional. If unspecified, the current directory is used.
</p>
</dd>
<dtclass="hdlist1">
--abort [path_to_workdir]
</dt>
<dd>
<p>
Abort a cherry-pick that required manual resolution and clean up its workdir.
The path to the drover workdir is optional. If unspecified, the current
directory is used.
</p>
</dd>
<dtclass="hdlist1">
--parent_checkout
</dt>
<dd>
@ -838,7 +858,37 @@ at least once to fetch the branches.</p></div>
<h4id="_merge_example">Merge Example</h4>
<divclass="paragraph"><p></p></div><divclass="listingblock"><divclass="content"><pre><code># Here's a commit (from some.committer) that we want to 'drover'.
<h4id="_merge_with_conflicts_example">Merge with Conflicts Example</h4>
<divclass="paragraph"><p></p></div><divclass="listingblock"><divclass="content"><pre><code># Here's a commit (from some.committer) that we want to 'drover'.
git drover applies a commit to a release branch\&. It creates a new workdir from an existing checkout to avoid downloading a new checkout without affecting the existing checkout\&. Creating a workdir requires symlinks so this does not work on Windows\&. See the EXAMPLE section for the equivalent sequence of commands to run\&.
git drover applies a commit to a release branch\&. It creates a new workdir from an existing checkout to avoid downloading a new checkout without affecting the existing checkout\&.
.sp
git drover does not support reverts\&. See the EXAMPLE section for the equivalent sequence of commands to run\&.
.SH"OPTIONS"
@ -54,6 +56,16 @@ The branch to cherry\-pick the commit to\&.
The commit to cherry\-pick\&.
.RE
.PP
\-\-continue [path_to_workdir]
.RS4
Continue a cherry\-pick that required manual resolution\&. The path to the drover workdir is optional\&. If unspecified, the current directory is used\&.
.RE
.PP
\-\-abort [path_to_workdir]
.RS4
Abort a cherry\-pick that required manual resolution and clean up its workdir\&. The path to the drover workdir is optional\&. If unspecified, the current directory is used\&.
.RE
.PP
\-\-parent_checkout
.RS4
The path to the chromium checkout to use as the source for a creating git\-new\-workdir workdir to use for cherry\-picking\&. If unspecified, the current directory is used\&.
@ -89,7 +101,54 @@ Before working with branches, you must \fIgclient sync \-\-with_branch_heads\fR
.nf
# Here\*(Aqs a commit (from some\&.committer) that we want to \*(Aqdrover\*(Aq\&.