From: Junio C Hamano <gitster@pobox.com>
To: Jari Aalto <jari.aalto@cante.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-reset.txt: Use commit~1 notation over commit^
Date: Wed, 01 Dec 2010 14:06:32 -0800 [thread overview]
Message-ID: <7vfwuhtafr.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: 877hftuvvz.fsf@picasso.cante.net
Jari Aalto <jari.aalto@cante.net> writes:
> What people appreciate, while learning, is constency. Sticking to one
> notation is better than giving multiple choices. And the "^" isn't
> exactly readable, don't you agree?
>
> HEAD^^^^^^^^
>
> Right. How many was there again?
There is no question that you need to really count them, and that is why
we invented HEAD~8 notation in the first place. It however is wrong to
use the above illustration to defend your change that replaces "HEAD^"
with "HEAD~1".
The thing is, you need to name/call the previous one a lot more often than
you need to call the eighth previous one. The previous one "HEAD~1" is
special because it directly relates to the current commit (it is the first
parent of the current commit) and that is why people often need to access
it.
And "HEAD^" is shorter and much easier to type, and more importantly, it
is more often used in the wild, so the readers of the documentation needs
to know it anyway to understand what other people do.
next prev parent reply other threads:[~2010-12-01 22:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 18:14 [PATCH] git-reset.txt: Use commit~1 notation over commit^ jari.aalto
2010-12-01 19:13 ` Drew Northup
2010-12-01 19:37 ` Jari Aalto
2010-12-01 22:01 ` Kevin Ballard
2010-12-01 22:49 ` Jari Aalto
2010-12-01 22:56 ` Kevin Ballard
2010-12-01 22:06 ` Junio C Hamano [this message]
2010-12-01 22:50 ` Jari Aalto
2010-12-02 0:07 ` Andreas Schwab
2010-12-02 5:37 ` Jari Aalto
2010-12-01 22:56 ` Santi Béjar
2010-12-02 5:39 ` Jari Aalto
2010-12-02 6:17 ` Miles Bader
2010-12-02 12:14 ` Jari Aalto
2010-12-02 12:51 ` Drew Northup
2010-12-02 13:17 ` Miles Bader
2010-12-02 13:20 ` jari
2010-12-02 17:44 ` Andreas Schwab
2010-12-02 17:55 ` Junio C Hamano
2010-12-02 18:46 ` Jeff King
2010-12-02 18:54 ` Junio C Hamano
2010-12-02 19:05 ` Jeff King
2010-12-02 2:46 ` 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=7vfwuhtafr.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).