diff options
author | Ramkumar Ramachandra <artagnon@gmail.com> | 2013-06-16 10:45:13 +0200 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2013-06-24 07:16:42 +0200 |
commit | 26cd160cb15635afd1c2937a3c15cfb256758323 (patch) | |
tree | 5307ca3e6aab73d1f391fbe28988b8151acb3cb7 /git-rebase.sh | |
parent | rebase: use a better reflog message (diff) | |
download | git-26cd160cb15635afd1c2937a3c15cfb256758323.tar.xz git-26cd160cb15635afd1c2937a3c15cfb256758323.zip |
rebase -i: use a better reflog message
Now that the "checkout" invoked internally from "rebase -i" knows to
honor GIT_REFLOG_ACTION, we can start to use it to write a better
reflog message when "rebase anotherbranch", "rebase --onto branch",
etc. internally checks out the new fork point. We will write:
rebase -i: checkout master
instead of the old
rebase -i
As all the calls git-rebase--interactive make to underlying git
commands that leave reflog messages are preceded by the internal
comment_for_reflog helper function, which uses the original value of
the GIT_REFLOG_ACTION variable it saw when it first started, the new
assignments to GIT_REFLOG_ACTION actively contaminate the value of
the variable, knowing that it will be reset to a sane value before
it is used again. This does not generally hold true but it should
suffice for now.
Signed-off-by: Ramkumar Ramachandra <artagnon@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'git-rebase.sh')
0 files changed, 0 insertions, 0 deletions