RE: What's in git.git (stable)

Yep.  Although you've persuaded me with the above example, I 
think this is the 
correct path.  It's not wise to add every bell and whistle 
just because we 
can.  As long as there is /a/ way to achieve every task, 
that's good enough, 
we don't need every way to achieve every task.  We might even 
argue that 
git's flexibility is what makes it harder to learn.  It's 
similar to UNIX in 
that respect - hard to learn, easy to use.

So we prefer to tell users "You can do what you want with these 3 commands,
since we don't want to confuse use with another option to do it with just
1"?

Andy

-- 
best regards

  Ray