From: Junio C Hamano <gitster@pobox.com>
To: "Stefan Näwe" <stefan.naewe@gmail.com>
Cc: git@vger.kernel.org, "Zeeshan Ali \(Khattak\)" <zeeshanak@gnome.org>
Subject: Re: Support of '^' as alias for 'HEAD^'
Date: Sat, 14 Jul 2012 13:34:19 -0700 [thread overview]
Message-ID: <7vr4se5bg4.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <7vzk725c86.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Sat, 14 Jul 2012 13:17:29 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> Stefan Näwe <stefan.naewe@gmail.com> writes:
>
>> Zeeshan Ali (Khattak <zeeshanak <at> gnome.org> writes:
>>>
>>> Many times I want to refer to 'HEAD^', 'HEAD^^' and sometimes even
>>> further up the tree. It would be really nice if I didn't have to type
>>> 'HEAD^' but could only type '^'. Bash completion make things easier
>>> but it automatically inserts a space immediately after HEAD so you
>>> have to hit backspace. I think this change would be good in general
>>> anyway.
>>
>> Or even '~1', '~3'.
>
> "^" has a problem when used with other things (does "log ^^2
> origin" mean "log HEAD^2..origin"? Or "log HEAD^^2 origin"), so I
> do not think it would never fly as an abbreviated syntax.
>
> While I see your "~<N>" much distasteful compared to "^", you still
s/dist/less dist/; sorry ;-)
> need to be a bit more careful when analysing the benefit of such an
> abbreviation. To shells used by many people, these mean tilde
> expansion ~<N> to refer to elements on the dirstack and you need to
> quote, perhaps like \~3.
next prev parent reply other threads:[~2012-07-14 20:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-14 0:39 Support of '^' as alias for 'HEAD^' Zeeshan Ali (Khattak)
2012-07-14 9:48 ` Stefan Näwe
2012-07-14 20:17 ` Junio C Hamano
2012-07-14 20:34 ` Junio C Hamano [this message]
2012-07-14 20:49 ` Zeeshan Ali (Khattak)
2012-07-14 21:26 ` Junio C Hamano
2012-07-14 22:24 ` Zeeshan Ali (Khattak)
2012-07-15 7:44 ` Jeff King
2012-07-15 17:45 ` Holger Hellmuth
2012-07-15 21:48 ` Zeeshan Ali (Khattak)
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=7vr4se5bg4.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=stefan.naewe@gmail.com \
--cc=zeeshanak@gnome.org \
/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).