End of line characters in bzr

[Nicholas Allen]

Thanks. I didn't notice that page ;-)

It seems like that is quite a big limitation in bazaar currently then. 
We work on Mac OSX, windows and occassionally Linux so it would be 
essential that bazaar does something sensible with the line endings. 
This is something that svn at least seems to do well (compared to bzr - 
it's about the only thing ;-)).

Any idea on when bazaar will handle line endings properly (is that a 1.0 
goal)?

Cheers,

Nick

Alexander Belchenko wrote:
> Nicholas Allen пишет:
>> Just wondering how bzr deals with EOL characters. In the repository 
>> they are stored only as \n but in working tree they use the native OS 
>> line ending style don't they?
>
> No. Bzr store lines as-is and use \n as line endings character.
> See: http://bazaar-vcs.org/LineEndings
>
> Actually problem is in fact that bzr don't store type of file: text or 
> binary and each time try to guess this.
>
>> I just wanted to try branching in bzr on our repository and copying 
>> the files from a subversion working copy of an svn branch into the 
>> bzr working tree and committing. But when I do so it says that every 
>> line changed and if I diff it then the only difference is the line 
>> end character (and of course the other changes I made in my svn 
>> branch working copy). If bzr uses the OS EOL character (and I'm sure 
>> that svn does too) then there should not be any difference in the EOL.
>>
>> Is there any way to get bzr to ignore end of line character changes 
>> and not commit them? If they are always stored in the repository as 
>> \n then shouldn't this just be the default option for commit, diff, 
>> and status?
>
>