From: Jari Aalto <jari.aalto@cante.net>
To: git@vger.kernel.org
Subject: Re: [PATCH] git-reset.txt: Use uniform HEAD~N notation in all examples
Date: Sat, 01 Sep 2007 23:40:55 +0300 [thread overview]
Message-ID: <veauqfu0.fsf@cante.net> (raw)
In-Reply-To: 20070901150153.GD7422@mediacenter.austin.rr.com
Shawn Bohrer <shawn.bohrer@gmail.com> writes:
> On Sat, Sep 01, 2007 at 02:40:22AM -0700, Junio C Hamano wrote:
>
>> Jari Aalto <jari.aalto@cante.net> writes:
>>
>> > Like:
>> >
>> > HEAD, HEAD~1, HEAD~2
>> >
>> > If the syntax is changed in the middle (as it was in manual page),
>> > that interrupts the kognitive flow of reading.
>> >
>> > HEAD, HEAD^, HEAD~2
>> >
>>
>> I still would prefer to teach people HEAD^ earlier. If you _REALLY_
>> insist, I can live with spelling the HEAD~2 as HEAD^^ for
>> consistency.
>
> Well I am a new user to git and I didn't find the mixed notation
> confusing at all. Perhaps this is because I read the tutorial first,
> then the git user manual which both explain this clearly.
Naturally one's learning path is naturally different. Did you come
from other SCM/VCS before intorduced to git?
> In either case I think eliminating either notation from the man pages is
> a bad idea.
That was not proposed. There a mnay pages that use and shoudl use the
^ notations. I was proposing that only (git-COMMAND) were dealt with.
After all, the ^ very differento to what other SCM/VCSs use.
Jari
--
Welcome to FOSS revolution: we fix and modify until it shines
next prev parent reply other threads:[~2007-09-01 20:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 17:47 [PATCH] git-reset.txt: Use uniform HEAD~N notation in all examples Jari Aalto
2007-08-31 19:00 ` Junio C Hamano
2007-09-01 8:39 ` Jari Aalto
2007-09-01 9:40 ` Junio C Hamano
2007-09-01 15:01 ` Shawn Bohrer
2007-09-01 20:40 ` Jari Aalto [this message]
2007-09-03 2:03 ` Miles Bader
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=veauqfu0.fsf@cante.net \
--to=jari.aalto@cante.net \
--cc=git@vger.kernel.org \
/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