git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
	Duy Nguyen <pclouds@gmail.com>,
	Git Mailing List <git@vger.kernel.org>,
	Michael J Gruber <git@drmicha.warpmail.net>,
	Jon Seymour <jon.seymour@gmail.com>
Subject: Re: [PATCH] Add new @ shortcut for HEAD
Date: Tue, 30 Apr 2013 13:20:51 -0500	[thread overview]
Message-ID: <CAMP44s28aQ7aDCBk=TwPJsb4xoyQMfx85DhaNB4P+XzbgctoPw@mail.gmail.com> (raw)
In-Reply-To: <CALkWK0=GbhALxX0G-ka5oAbixoJv4uKPHAx5LPezgTyGxW_3MQ@mail.gmail.com>

On Tue, Apr 30, 2013 at 12:40 PM, Ramkumar Ramachandra
<artagnon@gmail.com> wrote:
> Junio C Hamano wrote:
>> If you accept only "@" but not "master@", that behaviour needs a
>> wrong world model to understand and justify (one of which is "@ is a
>> synonym for HEAD").  If your rule is "In $anything@{$n}, you can
>> drop {$n} when $n==0", then HEAD@{0} becomes HEAD@ and master@{0}
>> becomes master@, and @{0} becomes @ naturally.
>
> Besides, you're going in the wrong direction this time.  You are
> trying to fit an explanation to something that is useless.  How is
> master@ useful?

It's not. The same way master^0^0~4 is not useful, yet it's works;
it's a logical result from the syntax.

-- 
Felipe Contreras

  parent reply	other threads:[~2013-04-30 18:51 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-29 19:35 [PATCH] Add new @ shortcut for HEAD Felipe Contreras
2013-04-29 19:43 ` Ramkumar Ramachandra
2013-04-29 20:01 ` Junio C Hamano
2013-04-29 20:14   ` Felipe Contreras
2013-04-29 20:24     ` Junio C Hamano
2013-04-29 20:38       ` Felipe Contreras
2013-04-29 21:01         ` Junio C Hamano
2013-04-29 20:02 ` Junio C Hamano
2013-04-29 20:23   ` Felipe Contreras
2013-04-29 21:36     ` Felipe Contreras
2013-04-29 22:50       ` Junio C Hamano
2013-04-30  0:53         ` Jonathan Nieder
2013-04-30 17:54           ` Junio C Hamano
2013-04-30 18:17             ` Felipe Contreras
2013-04-29 22:38 ` Junio C Hamano
2013-04-29 22:49   ` Felipe Contreras
2013-04-29 23:06     ` Junio C Hamano
2013-04-29 23:10       ` Felipe Contreras
2013-04-30  5:54 ` Duy Nguyen
2013-04-30  6:10   ` Felipe Contreras
2013-04-30  6:17     ` Duy Nguyen
2013-04-30  6:20       ` Felipe Contreras
2013-04-30  6:30     ` Duy Nguyen
2013-04-30  7:55       ` Felipe Contreras
2013-04-30  7:09   ` Michael Haggerty
2013-04-30  7:35     ` Ramkumar Ramachandra
2013-04-30 10:16       ` Duy Nguyen
2013-04-30 11:10         ` Ramkumar Ramachandra
2013-04-30 18:54       ` Ramkumar Ramachandra
2013-04-30 10:12     ` Duy Nguyen
2013-04-30 17:22   ` Junio C Hamano
2013-04-30 17:37     ` Ramkumar Ramachandra
2013-04-30 17:40     ` Ramkumar Ramachandra
2013-04-30 17:56       ` Junio C Hamano
2013-04-30 18:04         ` Ramkumar Ramachandra
2013-04-30 18:20       ` Felipe Contreras [this message]
2013-04-30 18:45         ` Ramkumar Ramachandra
2013-04-30 22:08           ` Felipe Contreras
2013-04-30 17:47     ` Felipe Contreras
2013-04-30 17:56       ` Jeff King
2013-04-30 18:18         ` Felipe Contreras
2013-04-30 19:42     ` Junio C Hamano
2013-04-30 19:53       ` Ramkumar Ramachandra
2013-04-30 20:05         ` Junio C Hamano
2013-04-30 20:37           ` Ramkumar Ramachandra
2013-04-30 19:59       ` Junio C Hamano
2013-04-30 22:17       ` Felipe Contreras
2013-04-30 22:27         ` Junio C Hamano
2013-04-30 22:38           ` Felipe Contreras
2013-04-30 22:42             ` Junio C Hamano
2013-04-30 22:53               ` Felipe Contreras
2013-04-30 23:00                 ` Felipe Contreras
2013-04-30 23:19                   ` Felipe Contreras
2013-04-30 23:24                     ` Junio C Hamano
2013-04-30  6:07 ` Duy Nguyen
2013-04-30  6:11   ` Felipe Contreras

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='CAMP44s28aQ7aDCBk=TwPJsb4xoyQMfx85DhaNB4P+XzbgctoPw@mail.gmail.com' \
    --to=felipe.contreras@gmail.com \
    --cc=artagnon@gmail.com \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jon.seymour@gmail.com \
    --cc=pclouds@gmail.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).