Bazaar says file is modified and revert command does not make the file unmodified

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Nicholas Allen wrote:
> It seems I had eol = native in my rules and the file was checked in by
> someone on a Windows machine with crlf line endings. So I guess that
> makes sense but it was a bit confusing ;-)
> 
> Nick
> 
> Nicholas Allen wrote:
>> Hi,
>>
>> I am experiencing a really weird bug in Bazaar. In my working tree it
>> tells me a file has been modified but I definitely have not touched
>> this file. When I run bzr revert Bazaar prints that it's modifying the
>> file back to what it was before but then bzr status still shows the
>> file as modified.
>>
>> There seems to be no way to make Bazaar think this file is not modified.
>>
>> Any ideas what this could be?
>>
>> Cheers,
>>
>> Nick
> 
> 
> 

So i think:
  rm file
  bzr revert file

Might work. But as you say, in the repo it may have CRLF, and you'll
always be creating LF on disk...

Does 'bzr diff' also show that the file is changed?

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkvHMIUACgkQJdeBCYSNAAOycgCgv9OTUEYZjoGw93s8Qz/5lZFq
WIQAn19bP9UWH6E7gV5WZfr4O4V0Pmps
=00wO
-----END PGP SIGNATURE-----