From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Git List <git@vger.kernel.org>
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH v3 6/7] rebase: write better reflog messages
Date: Wed, 19 Jun 2013 13:34:48 +0530 [thread overview]
Message-ID: <1371629089-27008-7-git-send-email-artagnon@gmail.com> (raw)
In-Reply-To: <1371629089-27008-1-git-send-email-artagnon@gmail.com>
Now that the "checkout" invoked internally from "rebase" 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: checkout master
instead of the old
rebase
The usage semantics of GIT_REFLOG_ACTION have changed; by appending to
GIT_REFLOG_ACTION directly, we risk appending to a prebuilt string like
"rebase: checkout mool" from a previous append, when we really intended
to append to the string "rebase". Solve this problem by introducing a
base_reflog_action variable that is different from GIT_REFLOG_ACTION.
Signed-off-by: Ramkumar Ramachandra <artagnon@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
git-am.sh | 4 +++-
git-rebase--am.sh | 7 +++++++
git-rebase.sh | 18 ++++++++++++++++--
3 files changed, 26 insertions(+), 3 deletions(-)
diff --git a/git-am.sh b/git-am.sh
index 1cf3d1d..74ef9ca 100755
--- a/git-am.sh
+++ b/git-am.sh
@@ -46,6 +46,8 @@ set_reflog_action am
require_work_tree
cd_to_toplevel
+base_reflog_action="$GIT_REFLOG_ACTION"
+
git var GIT_COMMITTER_IDENT >/dev/null ||
die "$(gettext "You need to set your committer info first")"
@@ -884,7 +886,7 @@ did you forget to use 'git add'?"
fi &&
git commit-tree $tree ${parent:+-p} $parent <"$dotest/final-commit"
) &&
- git update-ref -m "$GIT_REFLOG_ACTION: $FIRSTLINE" HEAD $commit $parent ||
+ git update-ref -m "$base_reflog_action: $FIRSTLINE" HEAD $commit $parent ||
stop_here $this
if test -f "$dotest/original-commit"; then
diff --git a/git-rebase--am.sh b/git-rebase--am.sh
index 34e3102..7fbeb35 100644
--- a/git-rebase--am.sh
+++ b/git-rebase--am.sh
@@ -5,11 +5,13 @@
case "$action" in
continue)
+ GIT_REFLOG_ACTION="$base_reflog_action"
git am --resolved --resolvemsg="$resolvemsg" &&
move_to_original_branch
return
;;
skip)
+ GIT_REFLOG_ACTION="$base_reflog_action"
git am --skip --resolvemsg="$resolvemsg" &&
move_to_original_branch
return
@@ -40,9 +42,11 @@ else
rm -f "$GIT_DIR/rebased-patches"
case "$head_name" in
refs/heads/*)
+ GIT_REFLOG_ACTION="$base_reflog_action: checkout $head_name"
git checkout -q "$head_name"
;;
*)
+ GIT_REFLOG_ACTION="$base_reflog_action: checkout $orig_head"
git checkout -q "$orig_head"
;;
esac
@@ -59,6 +63,9 @@ else
return $?
fi
+ # always reset GIT_REFLOG_ACTION before calling any external
+ # scripts; they have no idea about our base_reflog_action
+ GIT_REFLOG_ACTION="$base_reflog_action"
git am $git_am_opt --rebasing --resolvemsg="$resolvemsg" <"$GIT_DIR/rebased-patches"
ret=$?
diff --git a/git-rebase.sh b/git-rebase.sh
index d0c11a9..6cdf9f8 100755
--- a/git-rebase.sh
+++ b/git-rebase.sh
@@ -47,6 +47,13 @@ set_reflog_action rebase
require_work_tree_exists
cd_to_toplevel
+# Should contain a base string like "rebase" (or "rebase -i (start)")
+# to which a more information like ": checkout foom" can be appended
+# to set the final GIT_REFLOG_ACTION. If you append to
+# GIT_REFLOG_ACTION directly, you risk appending to a prebuilt string
+# like "rebase: checkout mool" from a previous append.
+base_reflog_action="$GIT_REFLOG_ACTION"
+
LF='
'
ok_to_skip_pre_rebase=
@@ -336,7 +343,8 @@ then
# Only interactive rebase uses detailed reflog messages
if test "$type" = interactive && test "$GIT_REFLOG_ACTION" = rebase
then
- GIT_REFLOG_ACTION="rebase -i ($action)"
+ GIT_REFLOG_ACTION="rebase -i ($1)"
+ base_reflog_action="$GIT_REFLOG_ACTION"
export GIT_REFLOG_ACTION
fi
fi
@@ -543,7 +551,11 @@ then
if test -z "$force_rebase"
then
# Lazily switch to the target branch if needed...
- test -z "$switch_to" || git checkout "$switch_to" --
+ if test -n "$switch_to"
+ then
+ GIT_REFLOG_ACTION="$base_reflog_action: checkout $switch_to"
+ git checkout "$switch_to" --
+ fi
say "$(eval_gettext "Current branch \$branch_name is up to date.")"
exit 0
else
@@ -568,6 +580,8 @@ test "$type" = interactive && run_specific_rebase
# Detach HEAD and reset the tree
say "$(gettext "First, rewinding head to replay your work on top of it...")"
+
+GIT_REFLOG_ACTION="$base_reflog_action: checkout $onto_name"
git checkout -q "$onto^0" || die "could not detach HEAD"
git update-ref ORIG_HEAD $orig_head
--
1.8.3.1.449.g41b32a4.dirty
next prev parent reply other threads:[~2013-06-19 8:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 8:04 [PATCH v3 0/7] Re-roll rr/rebase-checkout-reflog Ramkumar Ramachandra
2013-06-19 8:04 ` [PATCH v3 1/7] t/t7512-status-help: test "HEAD detached from" Ramkumar Ramachandra
2013-06-19 8:04 ` [PATCH v3 2/7] wt-status: remove unused field in grab_1st_switch_cbdata Ramkumar Ramachandra
2013-06-19 8:04 ` [PATCH v3 3/7] t/t2012-checkout-last: test "checkout -" after a rebase Ramkumar Ramachandra
2013-06-19 9:10 ` Johannes Sixt
2013-06-19 9:41 ` Ramkumar Ramachandra
2013-06-19 8:04 ` [PATCH v3 4/7] status: do not depend on rebase reflog messages Ramkumar Ramachandra
2013-06-19 8:04 ` [PATCH v3 5/7] checkout: respect GIT_REFLOG_ACTION Ramkumar Ramachandra
2013-06-19 8:04 ` Ramkumar Ramachandra [this message]
2013-06-24 3:26 ` [PATCH v3 6/7] rebase: write better reflog messages Junio C Hamano
2013-06-24 7:07 ` Ramkumar Ramachandra
2013-06-24 7:57 ` Junio C Hamano
2013-06-24 8:12 ` Ramkumar Ramachandra
2013-06-19 8:04 ` [PATCH v3 7/7] rebase -i: " Ramkumar Ramachandra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1371629089-27008-7-git-send-email-artagnon@gmail.com \
--to=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).