From: Eric Sunshine <sunshine@sunshineco.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Git List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>,
Ramkumar Ramachandra <artagnon@gmail.com>,
Jeff King <peff@peff.net>, Duy Nguyen <pclouds@gmail.com>
Subject: Re: [PATCH v3] Add new @ shortcut for HEAD
Date: Wed, 1 May 2013 06:12:05 -0400 [thread overview]
Message-ID: <CAPig+cSQeU8BaaPm7GfCUxtsVj1Ce31ygBLdkb5WN8o4aNMAow@mail.gmail.com> (raw)
In-Reply-To: <1367401888-21055-1-git-send-email-felipe.contreras@gmail.com>
On Wed, May 1, 2013 at 5:51 AM, Felipe Contreras
<felipe.contreras@gmail.com> wrote:
> So HEAD@{0}~0^0 is too much to type, but we can remove '^0', and we can
> remove '~0', and we can remove 'HEAD', which leaves us with @{0}, but we
> can't remove '{0}'?
>
> This patch allows '@' to be the same as 'HEAD'.
>
> So now we can use 'git show @~1', and all that goody goodness.
>
> Until now '@' was a valid name, but it conflicts with this idea, so lets
s/lets/let's/ (contraction of "let us")
> make it invalid. Probably very few people, if any, used this name.
>
> Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
next prev parent reply other threads:[~2013-05-01 10:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 9:51 [PATCH v3] Add new @ shortcut for HEAD Felipe Contreras
2013-05-01 10:12 ` Eric Sunshine [this message]
2013-05-01 10:31 ` Thomas Adam
2013-05-01 14:23 ` "lets" vs. "let's" (was: Re: [PATCH v3] Add new @ shortcut for HEAD) Marc Branchaud
2013-05-01 17:18 ` "lets" vs. "let's" Junio C Hamano
2013-05-01 17:53 ` [PATCH v3] Add new @ shortcut for HEAD Junio C Hamano
2013-05-01 18:33 ` Felipe Contreras
2013-05-01 22:08 ` Junio C Hamano
2013-05-01 22:35 ` Felipe Contreras
2013-05-01 22:59 ` Junio C Hamano
2013-05-01 23:14 ` Felipe Contreras
2013-05-02 2:33 ` Felipe Contreras
2013-05-06 14:48 ` Junio C Hamano
2013-05-01 22:56 ` Junio C Hamano
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=CAPig+cSQeU8BaaPm7GfCUxtsVj1Ce31ygBLdkb5WN8o4aNMAow@mail.gmail.com \
--to=sunshine@sunshineco.com \
--cc=artagnon@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
/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).