[PREVIEW] line-endings support

[Alexander Belchenko]

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

My branch with eol support is ready for review and testing with real data.
This work started 3 weeks ago after 1.3 release. I don't merged latest bzr.dev
changes.

The branch mirror is here:
	https://code.launchpad.net/~bialix/bzr/eol

Patch against bzr.dev is attached.

Used simple file properties implementation does not require format upgrade
and eol support will work with any working tree format (WT2, 3 and 4).

To start using eol support you need set 'eol' property for some files
or file mask, e.g.:

$ bzr prop-set *.txt eol native
$ bzr prop-set *.py eol LF
$ bzr prop-set binary.file eol exact

You can use following values:
~  * exact (default)
~  * native
~  * LF
~  * CRLF
~  * CR

If eol property is not set then 'exact' value will be used.

Binary files are auto-detected and eol-conversion disabled for them, even if you set
'eol' property to some value different from 'exact'. utf-16 files consider to be binary.

Text files with non-exact eols saved with LF internally. When bzr write file to disk it
uses specified eol. Mangling of eol on disk does not triggered as false changes. When file
read from disk any kind of eol normalized to LF.

If you discover a bug then don't file bug report in launchpad.net/bzr because this work
is not complete yet. Report about found bugs or incorrect behavior in ML or mail me directly.

I'll build bzr.exe for my own dogfooding. If you wanna it say so.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFH+7dQzYr338mxwCURAl4wAJ47m3h3c/8kHYkCK9qeOsBPm3qMMACcD5UY
XIw+gUMwBO1qugmZX97qxdQ=
=X1gr
-----END PGP SIGNATURE-----
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: eol.tests-3341.patch
Url: https://lists.ubuntu.com/archives/bazaar/attachments/20080408/2a0410bd/attachment-0001.diff