From: Jakub Narebski <jnareb@gmail.com>
To: Joshua Jensen <jjensen@workspacewhiz.com>
Cc: Junio C Hamano <gitster@pobox.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: git rebase --abort of an --onto run does not checkout the originating branch
Date: Thu, 28 Oct 2010 09:22:08 -0700 (PDT) [thread overview]
Message-ID: <m3wrp2gufb.fsf@localhost.localdomain> (raw)
In-Reply-To: <4CC8E84C.3030709@workspacewhiz.com>
Joshua Jensen <jjensen@workspacewhiz.com> writes:
> I'll just have to remember where I was when I started the rebase,
> perform the abort, and checkout the originating branch.
"git checkout -" (or its generalization "git checkout @{-<n>}").
P.S. This is discounting whether there is bug in "git rebase --abort"
after using it with `--onto` or not.
--
Jakub Narebski
Poland
ShadeHawk on #git
prev parent reply other threads:[~2010-10-28 16:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 17:01 git rebase --abort of an --onto run does not checkout the originating branch Joshua Jensen
2010-10-22 19:15 ` Junio C Hamano
2010-10-28 3:04 ` Joshua Jensen
2010-10-28 16:22 ` Jakub Narebski [this message]
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=m3wrp2gufb.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jjensen@workspacewhiz.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).