eol management

I don't think bzr supports eol conversion in any way, and quite frankly don't think it's necessary. Today, most tools can handle different line endings just fine. And if you think about it, the line endings are the easier part. Things get more interesting with the encoding, like Windows-1252 or UTF-8 (not very interesting if you're plain ASCII, I admit).
I'd recommend to put up rules for your project, like "all text files must be UTF-8, LF", "all images must be PNG or JPEG", "all file names must be lowercase and contain [a-z_] only", or whatever you come up with, and add automated tests to the project to check the _structure_ of the files, just like you would add tests for your code's _behavior_.
Just my two cents...

hi,
thanks for your advice -)
The real problem is that we want to migrate a lot of projects from cvs to bazaar and it seems very difficult to change files by hand. This is because CVS client under XP add automatically CR to every ascii file downloaded (and remove CR in commit)

But maybe we ought to consider our problem for another point of view:
which files are necessary to be converted (adding CR) when we want to use then under XP ?
Maybe we surprisingly discover they are a small set...
In addition we ought to force every XP editor to set delimiter=unix, wouldn't we ?
Thanks

eol handling is still a planned feature, it has just been delayed lately. Delayed, but certainly not abandoned, see:
http://bundlebuggy.aaronbentley.com/project/bzr/request/<4880CF60.2080805%40canonical.com>

Hello,
does someone have any news concerning the eol management? We would really like to have something like the eol property of subversion. The solution that is proposed in the bazaar help (bzr help eol) isn't an option. When the rule eol=native is added to the rules, all files are marked as modified.

David

Hi David and others,

end-of-line conversion is supported in bzr 2.0 and later. For best results we would recommend either 2.0.2 or a 2.1beta.

> The solution that is proposed in the bazaar help (bzr help eol) isn't an option.
> When the rule eol=native is added to the rules, all files are marked as modified.

Can you please open a separate question explaining just what the problem is, and we will try to help.