Re: [PATCH] Documentation/git-reset.txt: Use HEAD~N syntax everywhere (unify examples)

[Robin Rosenberg <robin.rosenberg.lists@dewire.com>]

lördagen den 2 februari 2008 skrev Jari Aalto:
> Yeah let's continue as usual. And every time you need to explain the
> difference, when you could just teach one. The is no doubt that
> 
>     HEAD~N
> 
> is superior to
> 
>     HEAD^^^^^^^^^^^^^^^^^^^^^^^
> 
> Count that. Optimizing keystrokes is hardly ever a brilliant idea from
> learning perspective.

You generally do not type HEAD~largeN, defining large as 3 or more. It's 
typically one or maybe two ^'s only. When the target is farther away you 
refer to the SHA-1 (or abbreviated form) tag or branch name instead, just to 
make sure you point to the right commit. 'HEAD~N' is useful for scripting and 
testing git itself, it's an advanced feature.

UI's that have only one way of accomplishing every task suck. Google this
term "the case against user interface consistency" for reasons why, in case
you haven't seen them for yourself.

-- robin