From: Junio C Hamano <gitster@pobox.com>
To: Martin von Zweigbergk <martin.von.zweigbergk@gmail.com>
Cc: git@vger.kernel.org, Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH] rebase --abort: do not update branch ref
Date: Sun, 21 Nov 2010 19:11:46 -0800 [thread overview]
Message-ID: <7v1v6evyq5.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: 1290337881-26449-1-git-send-email-martin.von.zweigbergk@gmail.com
Martin von Zweigbergk <martin.von.zweigbergk@gmail.com> writes:
> diff --git a/git-rebase.sh b/git-rebase.sh
> index ec08f9c..3d194b1 100755
> --- a/git-rebase.sh
> +++ b/git-rebase.sh
> @@ -278,12 +278,17 @@ do
> if test -d "$dotest"
> then
> GIT_QUIET=$(cat "$dotest/quiet")
> - move_to_original_branch
> else
> dotest="$GIT_DIR"/rebase-apply
> GIT_QUIET=$(cat "$dotest/quiet")
> - move_to_original_branch
> fi
Micronit. It appears that GIT_QUIET is set to the same value in either
case, so perhaps you would also want to move it outside of the if block,
i.e.
test -d "$dotest" || dotest="$GIT_DIR/rebase-apply"
GIT_QUIET=$(cat "$dotest/quiet)
... your rewrite to move_to_original_branch here ...
no? Staring at it further, I wonder who pays attention to GIT_QUIET in
this codepath that will soon exit, though.
> + head_name="$(cat "$dotest"/head-name)" &&
> + case "$head_name" in
> + refs/*)
> + git symbolic-ref HEAD $head_name ||
> + die "Could not move back to $head_name"
> + ;;
> + esac
> git reset --hard $(cat "$dotest/orig-head")
> rm -r "$dotest"
> exit
next prev parent reply other threads:[~2010-11-22 3:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-21 11:11 [PATCH] rebase --abort: do not update branch ref Martin von Zweigbergk
2010-11-21 19:20 ` [PATCH] t3407: make reflog check stricter Martin von Zweigbergk
2010-11-22 3:11 ` Junio C Hamano [this message]
2010-11-22 12:23 ` [PATCH] rebase --abort: do not update branch ref Martin von Zweigbergk
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7v1v6evyq5.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=martin.von.zweigbergk@gmail.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.
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 NNTP newsgroup(s).