git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC/largely untested/PATCH] sha1_name: interpret ~n as HEAD~n

From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date
May 2, 2011, 20:14 UTC
Message-ID
<vpq62pssvun.fsf@bauges.imag.fr>
In-Reply-To
<4DBEEEAA.3000004@drmicha.warpmail.net>
Michael J Gruber <git@drmicha.warpmail.net> writes:
Show 6 quoted lines
>> 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/
Previous: Michael J Gruber
Message 17 of 17 in “sha1_name: interpret ~n as HEAD~n”
  1. sha1_name: interpret ~n as HEAD~nMichael J Gruber, Apr 29, 2011
  2. Junio C HamanoApr 29, 2011
  3. Michael J GruberMay 1, 2011
  4. Matthieu MoyMay 1, 2011
  5. Junio C HamanoMay 1, 2011
  6. Matthieu MoyMay 1, 2011
  7. Jeff KingApr 29, 2011
  8. Sverre RabbelierApr 29, 2011
  9. Mikael MagnussonMay 7, 2011
  10. Andreas SchwabApr 29, 2011
  11. Junio C HamanoApr 30, 2011
  12. Andreas SchwabApr 30, 2011
  13. Michael J GruberMay 2, 2011
  14. Michael J GruberMay 2, 2011
  15. Junio C HamanoMay 2, 2011
  16. Michael J GruberMay 2, 2011
  17. Matthieu MoyMay 2, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.