From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: "Michael J Gruber" <git@drmicha.warpmail.net>
Cc: "Junio C Hamano" <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [RFC/largely untested/PATCH] sha1_name: interpret ~n as HEAD~n
Date: Sun, 01 May 2011 11:04:22 +0200 [thread overview]
Message-ID: <vpqoc3mg5bd.fsf@bauges.imag.fr> (raw)
In-Reply-To: <1304238652.9638.1446946253@webmail.messagingengine.com> (Michael J. Gruber's message of "Sun, 01 May 2011 10:30:52 +0200")
"Michael J Gruber" <git@drmicha.warpmail.net> writes:
> On Fri, 29 Apr 2011 09:21 -0700, "Junio C Hamano" <gitster@pobox.com>
> wrote:
>> Michael J Gruber <git@drmicha.warpmail.net> writes:
>>
>> > HEAD~n is often used for rebase invocations etc.
>>
>> I thought rebase invocations these days use @{u}.
>>
>
> I meant "rebase -i", sorry. And in fact I mostly mean those cases where
> I want to "amend" a commit which is not the top most one.
>
> Michael
... and Junio is right that
git rebase -i @{u}
usually does the right thing: let you amend any of the unpushed commits.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2011-05-01 9:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 15:53 [RFC/largely untested/PATCH] sha1_name: interpret ~n as HEAD~n Michael J Gruber
2011-04-29 16:21 ` Junio C Hamano
2011-05-01 8:30 ` Michael J Gruber
2011-05-01 9:04 ` Matthieu Moy [this message]
2011-05-01 18:34 ` Junio C Hamano
2011-05-01 21:21 ` Matthieu Moy
2011-04-29 22:34 ` Jeff King
2011-04-29 23:23 ` Sverre Rabbelier
2011-05-07 2:24 ` Mikael Magnusson
2011-04-29 23:31 ` Andreas Schwab
2011-04-30 5:33 ` Junio C Hamano
2011-04-30 9:09 ` Andreas Schwab
2011-05-02 8:42 ` Michael J Gruber
[not found] ` <BANLkTinxszGhtYobuvci5Yi8eTHW+pi2wA@mail.gmail.com>
2011-05-02 11:04 ` Michael J Gruber
2011-05-02 16:33 ` Junio C Hamano
2011-05-02 17:49 ` Michael J Gruber
2011-05-02 20:14 ` Matthieu Moy
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=vpqoc3mg5bd.fsf@bauges.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=git@drmicha.warpmail.net \
--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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.