David Kastrup <d...@gnu.org> writes:
> Stephen Leake <stephen_le...@stephe-leake.org> writes:
>> David Kastrup <d...@gnu.org> writes:
>>> "do the right thing" commands also tend to do the wrong thing
>>> occasionally with potentially disastrous results when they are used
>>> in scripts where the followup actions rely on the actual result.
>> That is bad, and should not be allowed. On the other hand, I have yet
>> to see an actual use case of bad behavior in this discussion.
That's about backward incompatibility, which is bad, but not what I was
talking about above.
Specifically, the proposed change is:
'git reset' will have different default actions depending on context:
- if a merge is not in progress, it will do 'git reset --mixed'
- if a merge is in progress, it will do 'git reset --merge'
Is there a use case where this will do the wrong thing?
Of course, I fully understand that not being able to come up with a
"wrong thing" use case is not the same as proving it cannot happen,
especially for a system as complex as git.
So it would be ok to say "we don't do that so we are not exposed to
But "wrong thing" use cases are more convincing :).
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html