Re: Short "git commit $file" syntax fails in the face of a resolved conflict

Nanako Shiraishi [off-list ref] writes:

But Nathan's first sentence is a different matter. I do not think it is
coming from the same confusion, and I think the question is a valid
one. Your answer does not explain why it is a bad idea to change the
behavior of "git commit path" to what "git commit -i path" does during a
merge.

The answer of course can be "because it changes the behavior people are
very much used to."

[jc: how many times do I have to ask you to wrap your lines, by the way?]

I tend to agree that "very much used to" argument carries much weight, but
I'll be sending a three-patch series to weatherbaloon the idea.