git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mikael Magnusson <mikachu@gmail.com>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: Jeff King <peff@peff.net>,
	Michael J Gruber <git@drmicha.warpmail.net>,
	git@vger.kernel.org
Subject: Re: [RFC/largely untested/PATCH] sha1_name: interpret ~n as HEAD~n
Date: Sat, 7 May 2011 04:24:04 +0200	[thread overview]
Message-ID: <BANLkTinsWpXYN+Zejph6toidZWFAkprcYw@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=7_-TF63Y9MRHZ_XirSUD6RAC9kw@mail.gmail.com>

On 30 April 2011 01:23, Sverre Rabbelier <srabbelier@gmail.com> wrote:
> Heya,
>
> On Sat, Apr 30, 2011 at 00:34, Jeff King <peff@peff.net> wrote:
>> So there really isn't a lot of consistency, I guess.  It also conflicts
>> a little with the shell's "~user" syntax, though presumably you don't
>> have users named "1" and "2".
>
> FWIW, I like the patch, mainly because I dislike typing HEAD~n (I
> usually mispel it as HEA~n) and agree with peff's analysis, we're such
> a long way from being any form of consistent that I don't see this
> breaking any user expectations.

Something I always set up in the skeleton dir
($prefix/share/git-core/templates) after installing git is
echo 'ref: HEAD' > h
it makes life so much easier :).

-- 
Mikael Magnusson

  reply	other threads:[~2011-05-07  2:24 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
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 [this message]
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=BANLkTinsWpXYN+Zejph6toidZWFAkprcYw@mail.gmail.com \
    --to=mikachu@gmail.com \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=srabbelier@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).