Am 6/18/2013 20:55, schrieb Ramkumar Ramachandra: > 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 > diff --git a/git-rebase--am.sh b/git-rebase--am.sh > index 34e3102..69fae7a 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" I haven't followed the topic closely, but I wonder why there are so many explicit assignments to GIT_REFLOG_ACTION. Is calling set_reflog_action (defined in git-sh-setup) the wrong thing to do? -- Hannes -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html