From: Jakub Narebski <jnareb@gmail.com>
To: Jari Aalto <jari.aalto@cante.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Documentation/git-reset.txt: Use HEAD~N syntax everywhere (unify examples)
Date: Sun, 03 Feb 2008 16:28:16 -0800 (PST) [thread overview]
Message-ID: <m3hcgp5zvs.fsf@localhost.localdomain> (raw)
In-Reply-To: <bq6x38lc.fsf@blue.sea.net>
Jari Aalto <jari.aalto@cante.net> writes:
> * Sun 2008-02-03 Dmitry Potapov <dpotapov@gmail.com>
> * Message-Id: 20080203193024.GV29522@dpotapov.dyndns.org
>>
>> ^-syntax is very natural to specify the _previous_ commit. Have you
>> notice we usually say "previous", not "one commit before"?
And you usually say "yesterday", "the day before" and not "1 day ago",
"2 days ago".
<rev>^ means (first) parent of commit-ish <rev>, or 'previous' commit.
<rev>~N means Nth parent in first-parent line of commit-ish <rev>; as
you can see full explanation is decidely longer.
> Only if you're grown with git. Everywhere else the concept of HEAD or
> TIP is more natural, thus progression:
>
> HEAD, HEAD~1, HEAD~2
The fact that other SCMs are poorer in expressive power doesn't mean
that we have to bend backwards and follow (well, not braindamaged,
just poor) other SCM limitations / conventions. Git is git is git :-)
So "everywhere else" doesn't matter any... unless in "SCM rosetta" or
something like that chapter in Git User's Manual.
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2008-02-04 0:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-02 1:41 [PATCH] Documentation/git-reset.txt: Use HEAD~N syntax everywhere (unify examples) Jari Aalto
2008-02-02 2:37 ` Johannes Schindelin
2008-02-02 2:59 ` Junio C Hamano
2008-02-02 8:44 ` Mike Hommey
2008-02-02 12:59 ` Jari Aalto
2008-02-02 13:37 ` Jakub Narebski
2008-02-02 20:10 ` Jari Aalto
2008-02-03 2:07 ` Johannes Schindelin
2008-02-02 16:18 ` J. Bruce Fields
2008-02-02 20:15 ` Jari Aalto
2008-02-02 22:39 ` Robin Rosenberg
2008-02-02 21:31 ` Junio C Hamano
2008-02-03 19:30 ` Dmitry Potapov
2008-02-03 23:48 ` Jari Aalto
2008-02-04 0:28 ` Jakub Narebski [this message]
2008-02-04 22:33 ` Dmitry Potapov
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=m3hcgp5zvs.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=jari.aalto@cante.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.