From: Junio C Hamano <gitster@pobox.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org, 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, 01 May 2013 15:56:58 -0700 [thread overview]
Message-ID: <7v8v3y48cl.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <7vsj264am4.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Wed, 01 May 2013 15:08:03 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> The thing is, HEAD@{0}~0^0 nor HEAD@{u}~0^0 is not a valid
> explanation why it is "@", either.
>
> But that does _not_ mean "@" is a good choice. Nor the explanation
Arrgh. It does not mean " '@' is a BAD choice ". '@' _is_ good.
But the point is that the explanation does not have to be a
technically incorrect "strip this, strip that".
prev parent reply other threads:[~2013-05-01 22:57 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
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 [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=7v8v3y48cl.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=artagnon@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--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).