[issue3139] hg bisect refuses to work if eol extension causes uncommitted changes

[Chr. Feuersaenger]

New submission from Chr. Feuersaenger <cfr at recommind.com>:

MOTIVATION:
As a user of hg bisect, I can run into "abort: outstanding uncommitted
changes" problems which cannot be solved without aborting the bisection.

Consequently, this issue might be a duplicate of the known feature request
"hg bisect should have --force flag". I report it here because "hg bisect
-f" might not only be a useful feature request - it might be a bugfix.

To see this, consider the following situation:
1. suppose you have a repository with EOL extension enabled
2. suppose you changed .hgeol somehow
3. the change will cause uncommitted changes, because the repository's
expectations on the line endings differ from the local version. 
In such a case, you see uncommitted local changes. Reverting these changes
does not help. Deleting the affected file and checking it out again does not
help either -- it *needs* to be committed.

4. now suppose that hg bisect runs over such a commit: it will refuse to
work due to uncommitted local changes, but one cannot revert the revision.

In our case, we aborted hg bisect, ran a clean update, and restarted the
bisection. This seemed to work.

Note: I am not authorized by my company to request official support for this
issue. This is merely a "private" tracker item in the hope that you
appreciate the feedback. Let me know if you need an "official" request.

----------
messages: 18242
nosy: feuersaenger
priority: bug
status: unread
title: hg bisect refuses to work if eol extension causes uncommitted changes

____________________________________________________
Mercurial issue tracker <bugs at mercurial.selenic.com>
<http://mercurial.selenic.com/bts/issue3139>
____________________________________________________