summaryrefslogtreecommitdiff
path: root/contrib/blameview
diff options
context:
space:
mode:
authorJonathan Nieder <jrnieder@gmail.com>2011-11-22 11:17:36 (GMT)
committerJunio C Hamano <gitster@pobox.com>2011-11-22 21:34:44 (GMT)
commit82433cdf4d888639cecddeca162d619cf370417e (patch)
treef079ee84d7364d734bfeb24ffc17b1451a26893c /contrib/blameview
parentb8c74690b20b7c4dd405f71d63bab325447356da (diff)
downloadgit-82433cdf4d888639cecddeca162d619cf370417e.zip
git-82433cdf4d888639cecddeca162d619cf370417e.tar.gz
git-82433cdf4d888639cecddeca162d619cf370417e.tar.bz2
revert: write REVERT_HEAD pseudoref during conflicted revert
When conflicts are encountered while reverting a commit, it can be handy to have the name of that commit easily available. For example, to produce a copy of the patch to refer to while resolving conflicts: $ git revert 2eceb2a8 error: could not revert 2eceb2a8... awesome, buggy feature $ git show -R REVERT_HEAD >the-patch $ edit $(git diff --name-only) Set a REVERT_HEAD pseudoref when "git revert" does not make a commit, for cases like this. This also makes it possible for scripts to distinguish between a revert that encountered conflicts and other sources of an unmerged index. After successfully committing, resetting with "git reset", or moving to another commit with "git checkout" or "git reset", the pseudoref is no longer useful, so remove it. Signed-off-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'contrib/blameview')
0 files changed, 0 insertions, 0 deletions