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

Re: [PATCH] Documentation/git-reset.txt: Use HEAD~N syntax everywhere (unify examples)

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Feb 3, 2008, 02:07 UTC
Message-ID
<alpine.LSU.1.00.0802030204400.7372@racer.site>
In-Reply-To
<abmj3ysj.fsf@blue.sea.net>
Hi,

[don't cut the Cc' list. It is rude. _Especially_ if you cull the one you are responding to. Or do you like people looking the other way when they talk to you?]

On Sat, 2 Feb 2008, Jari Aalto wrote:
Show 10 quoted lines
> * Sat 2008-02-02 Jakub Narebski <jnareb@gmail.com>
> * Message-Id: m3d4rf7a4r.fsf@localhost.localdomain
> > Jari Aalto <jari.aalto@cante.net> writes:
> >> I use HEAD~1 always, because I think the consistency in learning the
> >> most important factor.
> >
> > "HEAD~1" and "HEAD~2" are not shorter than original notation.
> 
> I'm afreaid that "optiomization" is seen a virtua in the manual pages. I 
> certainly do not wish to use "shorter", if it would mean "less readable"

IMO this is not just a matter of "shorter" or "longer". People familiar with Git use both forms. So if you want to be able to receive help from Git experts, you better understand both forms.

That's why Git newbies have to learn about _both_ syntaxes right away. Keeping them dumb serves _noone_.

Ciao, Dscho

Previous: Jari AaltoNext: J. Bruce Fields
Message 8 of 16 in “Documentation/git-reset.txt: Use HEAD~N syntax everywhere (unify examples)”
  1. Documentation/git-reset.txt: Use HEAD~N syntax everywhere (unify examples)Jari Aalto, Feb 2, 2008
  2. Johannes SchindelinFeb 2, 2008
  3. Junio C HamanoFeb 2, 2008
  4. Mike HommeyFeb 2, 2008
  5. Jari AaltoFeb 2, 2008
  6. Jakub NarebskiFeb 2, 2008
  7. Jari AaltoFeb 2, 2008
  8. Johannes SchindelinFeb 3, 2008
  9. J. Bruce FieldsFeb 2, 2008
  10. Jari AaltoFeb 2, 2008
  11. Robin RosenbergFeb 2, 2008
  12. Junio C HamanoFeb 2, 2008
  13. Dmitry PotapovFeb 3, 2008
  14. Jari AaltoFeb 3, 2008
  15. Jakub NarebskiFeb 4, 2008
  16. Dmitry PotapovFeb 4, 2008

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.