[Monotone-devel] Re: line endings as project policy

[Koen Kooi]

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

Justin Patrin schreef:
> On 11/21/06, Derek Scherger <address@hidden> wrote:

>> So, would this be better as a (shared and versioned) project policy
>> entry with line ending styles specified by file name patterns. It seems
>> like it would handle the case of added files, that match some policy
>> pattern, better. I'm not sure how policy *changes* would work though.
>> i.e. suppose the eol policy for .sh files is set to LF after a few .sh
>> files have already been added incorrectly. How do the pre-existing files
>> get fixed up?
>>
> 
> Ugh.
> 
> I haven't read the line endings with 0.31 thread yet but...ugh. Is it
> really necessary to mangle line endings when checking out files? I
> mean really....shouldn't people just use a capable text editor if
> they're contributing to a project?

Let's look at another use case:

In the openembedded project we have builddescriptions ('recipes') that can 
reference
patches and most of the time we store those patches in the SCM as well. No 
problem there.
Till some audiojunkies want to patch libfaac (or libfaad2, I forget) which 
source is in
CRLF form. At the time we were using bitkeeper which converted the patch to CR 
'because
you're on UNIX', so after reading the docs I checked in the patch *again* 
disabling the
EOLN_NATIVE flag. I could checkout the patch as CRLF, but other couldn't, 
unless they
frobbed the EOLN_NATIVE flag locally. We ended up storing the patch on a remote 
server so
the buildsystem would fetch it with wget instead of from the SCM.
Last week I checked in (into mtn) a CRLF patch and ... *drumroll* it worked!

I hope this usecase will be supported in the new and shiny policy stuff :)

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFFZBGHMkyGM64RGpERAlQHAKC4CRtTsLeZNiOZW9EwSA0fVVsINQCaA/zw
nP622I+1iXqi3bzQhxAPHyw=
=bUiy
-----END PGP SIGNATURE-----