author | Luben Tuikov <ltuikov@yahoo.com> | |
Thu, 12 Oct 2006 21:52:42 +0000 (14:52 -0700) | ||
committer | Junio C Hamano <junkio@cox.net> | |
Mon, 16 Oct 2006 06:06:31 +0000 (23:06 -0700) | ||
commit | a9cb3c6ecb97c4734423045f47899e03f135d3bd | |
tree | fa2f08dac9932d1d5e20bedcecc2e40e17bc2d25 | tree | snapshot |
parent | 1974bf620b436b014bfe86179ff76485610a4887 | commit | diff |
git-revert with conflicts to behave as git-merge with conflicts
In a busy project, reverting a commit almost always results
in a conflict between one or more files (depending on the
commit being reverted). It is useful to record this
conflict in the commit-to-be message of the resulting commit
(after the resolve). The process now becomes:
git-revert <SHA-1>
<git complains and prints failed automatic>
<user manually resolves>
git-update-index <resolved files>
git-commit -s
And the commit message is now a merge of the revert commit
message and the conflict commit message, giving the user a
chance to edit it or add more information:
Signed-off-by: Luben Tuikov <ltuikov@yahoo.com>
Signed-off-by: Junio C Hamano <junkio@cox.net>
In a busy project, reverting a commit almost always results
in a conflict between one or more files (depending on the
commit being reverted). It is useful to record this
conflict in the commit-to-be message of the resulting commit
(after the resolve). The process now becomes:
git-revert <SHA-1>
<git complains and prints failed automatic>
<user manually resolves>
git-update-index <resolved files>
git-commit -s
And the commit message is now a merge of the revert commit
message and the conflict commit message, giving the user a
chance to edit it or add more information:
Signed-off-by: Luben Tuikov <ltuikov@yahoo.com>
Signed-off-by: Junio C Hamano <junkio@cox.net>
git-commit.sh | diff | blob | history | |
git-revert.sh | diff | blob | history |