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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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:

> * Sat 2008-02-02 Jakub Narebski <jnareb@xxxxxxxxx>
> * Message-Id: m3d4rf7a4r.fsf@xxxxxxxxxxxxxxxxxxxxx
> > Jari Aalto <jari.aalto@xxxxxxxxx> 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

-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux