Re: [PATCH] Proof-of-concept patch to remember what the detached HEAD was

Hi,

On Wed, 14 Oct 2009, Nicolas Pitre wrote:

On Wed, 14 Oct 2009, Jeff King wrote:

quoted

On Wed, Oct 14, 2009 at 05:56:52PM -0700, Junio C Hamano wrote:

quoted

Nicolas Pitre [off-list ref] writes:

quoted

Can't the user confusion be dealt with through some means other than 
making the tool less flexible?  I don't mind extra help message to be 
displayed after a headless commit is made for example.  But trying to 
make the tool more friendly should perhaps come from better education 
rather than added restrictions.

My thoughts only.

I actually share that but there apparently are people who have given up on
the education route.

I am personally undecided on this issue (my "this is the best option"
was the best of "a -f switch to commit, an 'expert' config option', or a
session-based option to commit").

But we really seem to have reached an impasse with how to proceed with
git ui.

People like Dscho are fed up with user complaints about parts of git
that can be unfriendly to new users. And I can understand that.

People like Dscho have to grow a thicker skin then.  There will _always_ 
be user complaints regardless of how balanced you try to make a UI.

You are seriously misreading my intentions, then.  Or my intelligence.

It is not about growing a thicker skin towards unmerited complaints.

It is about shedding the thick skin when there are merited complaints, and 
some people are just too used to the old ways to understand that some of 
the complaints have _a lot_ of merit.

It is just like with the olden days when only a precious few could drive 
cars, and maintained that it _is_ hard to drive a car, and _not_ everybody 
can do it _because_ you will have a breakdown with the car and you _have_ 
to be able to fix it yourself.

Fast-forward a hundred years.

None of this is true any longer.

None.

Guess what?  In these days, we do not need a hundred years.  Four is 
plenty enough.  We have a lot of Git users who do not understand the inner 
workings of Git.  And why should they need to?

Who are you to say they should?

We, the old Gits need to change.  Not the many other people.

Remember: you do not know how exactly the clutch interacts with the 2nd 
cylinder of the engine.  And you do not _need_ to.

Neither should Git users need to.

Ciao,
Dscho