diff options
| author | Victor Boivie <victor.boivie@sonyericsson.com> | 2010-11-11 20:36:39 +0100 |
|---|---|---|
| committer | Shawn O. Pearce <sop@google.com> | 2011-04-07 17:19:06 -0400 |
| commit | d572a13021b0430eddf83e9caedc9d5add693c62 (patch) | |
| tree | a0dfe1a74aded3d9266eef72ee9ceec4cc9ef5a4 /git_config.py | |
| parent | 3ba5f95b46f06ed3d7382346de29ac550d749ec9 (diff) | |
| download | git-repo-d572a13021b0430eddf83e9caedc9d5add693c62.tar.gz | |
Added repo cherry-pick commandv1.7.4.3
It is undesired to have the same Change-Id:-line for two separate
commits, and when cherry-picking, the user must manually change it.
If this is not done, bad things may happen (such as when the user
is uploading the cherry-picked commit to Gerrit, it will instead
see it as a new patch-set for the original change, or worse).
repo cherry-pick works the same was as git cherry-pick, except that
it replaces the Change-Id with a new one and adds a reference
back to the commit from where it was picked.
On failures (when git can not successfully apply the cherry-picked
commit), instructions will be written to the user.
Change-Id: I5a38b89839f91848fad43386d43cae2f6cdabf83
Diffstat (limited to 'git_config.py')
0 files changed, 0 insertions, 0 deletions