From: Jari Aalto <jari.aalto@cante.net>
To: git@vger.kernel.org
Subject: Re: [PATCH] git-reset.txt: Use commit~1 notation over commit^
Date: Wed, 01 Dec 2010 21:37:52 +0200 [thread overview]
Message-ID: <877hftuvvz.fsf@picasso.cante.net> (raw)
In-Reply-To: 1291230820.11917.25.camel@drew-northup.unet.maine.edu
2010-12-01 21:13 Drew Northup <drew.northup@maine.edu>:
> "~" examples is actually a disservice to the documentation reader in a
Well. What I can say. I have witnessed close hand for thousands of
learners. Unfortunately they don't get educated that way. Bright people
may. But I'd rather address average Joe who is switching from SVN or the
like.
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?
Besides, the "^" key was probably inverted to work easily in US keybord.
It is not so in other parts of the world.
The fine print can be reserved to git-rev-parse(1) where you can get all
the details.
Jari
next prev parent reply other threads:[~2010-12-01 19:40 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 [this message]
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
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=877hftuvvz.fsf@picasso.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 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.