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: Thu, 02 Dec 2010 14:14:11 +0200 [thread overview]
Message-ID: <87bp54s770.fsf@picasso.cante.net> (raw)
In-Reply-To: buo39qg8zrf.fsf@dhlpc061.dev.necel.com
2010-12-02 08:17 Miles Bader <miles@gnu.org>:
> Jari Aalto <jari.aalto@cante.net> writes:
>
>>> Additionaly, you must know about the ^ notation. That is the only way
>>> refer to the second parent HEAD^2, for example.
>>
>> If "must" is a requirement, I have to regret that there has yet to have
>> been a situation where I would ahve a need to refer to "second parent".
>>
>> I guess most of the basic features can be used without it.
>
> It doesn't matter. There needs to be a better reason than "Jari doesn't
> like it."
This has nothing to do with liking. It how infomation is read. When
information is consistent, it lessens cognitive load.
In the "fine print" git-rev-parse(1) there can be the gory details.
most of the commenters probably are already experts and therefor wear
"expert glasses on". It's not necessarily the same for starters.
Certainly not when you try to teach 100 people. One form is much better
in that situation than variations. You only do it at the end:
"[After finishing 6 week training] Btw, if you need more details
look at...."
Experts can later pick anything they want.
Jari
next prev parent reply other threads:[~2010-12-02 12:14 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
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 [this message]
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=87bp54s770.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.