From: Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date: Mon, 02 May 2011 20:14:56 GMT
Subject: Re: [RFC/largely untested/PATCH] sha1_name: interpret ~n as HEAD~n
Message-ID: <vpq62pssvun.fsf@bauges.imag.fr>
In-Reply-To: <4DBEEEAA.3000004@drmicha.warpmail.net>

Michael J Gruber <git@drmicha.warpmail.net> writes:

>> I thought we already ruled out ~n because many shells think ~n is a path.
>
> You have, apparently ;)
>
> unquoted ~0 conflicts, but unquoted ~n conflicts only when you use pushd
> (and the stack has n entries; or n+-1, I can't count either...).

The problem is that it makes the behavior rather unpredictible for
non-expert:

git log ~2 # great
pushd
git log ~2 # still great
pushd
git log ~2 # WTF ?

so we can't teach new users the ~N syntax without quoting if we don't
want them to get bad surprises later. \~N is not terribly bad, but I
don't think it has a big added value compared to HEAD~N.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/