2009/6/6 Mark Hammond :
> Paul Moore wrote:
>>
>> 2009/6/5 Nick Coghlan :
>>>
>>> Dirkjan Ochtman wrote:
>
> Essentially, pcbuild.sln is a binary file, and should be treated as
> such. Maybe it's an error in the Subversion setup that it's treated as
> text at all...
Yes, i
Paul Moore wrote:
2009/6/5 Nick Coghlan :
Dirkjan Ochtman wrote:
Essentially, pcbuild.sln is a binary file, and should be treated as
such. Maybe it's an error in the Subversion setup that it's treated as
text at all...
Yes, it certainly seems that way.
Except it isn't a binary file - it's a t
2009/6/5 Nick Coghlan :
> Dirkjan Ochtman wrote:
>>> Essentially, pcbuild.sln is a binary file, and should be treated as
>>> such. Maybe it's an error in the Subversion setup that it's treated as
>>> text at all...
>>
>> Yes, it certainly seems that way.
>
> Except it isn't a binary file - it's a t
Dirkjan Ochtman wrote:
>> Essentially, pcbuild.sln is a binary file, and should be treated as
>> such. Maybe it's an error in the Subversion setup that it's treated as
>> text at all...
>
> Yes, it certainly seems that way.
Except it isn't a binary file - it's a text file with CRLF line endings.
On Thu, Jun 4, 2009 at 4:20 PM, Paul Moore wrote:
> Silly question, but given that Mercurial itself does *no* conversion,
> and CRLF is the only valid form for that file, why shouldn't the file
> be checked into the repository with CRLF endings, and that's the end
> of it (apart from misconfigured
On Thu, Jun 04, 2009 at 03:20:56PM +0100, Paul Moore wrote:
> Essentially, pcbuild.sln is a binary file, and should be treated as
> such. Maybe it's an error in the Subversion setup that it's treated as
> text at all...
Subversion has a built-in notion of eol-conversion (don't know if it was
us
2009/6/4 Dirkjan Ochtman :
> On Thu, Jun 4, 2009 at 3:02 PM, Jason R. Coombs wrote:
>> I wanted to share this with the community in case anyone else runs into this
>> issue. Also, if there's a recommended procedure for addressing this issue
>> (and others that might arise due to non-native line
On Thu, Jun 4, 2009 at 3:02 PM, Jason R. Coombs wrote:
> I wanted to share this with the community in case anyone else runs into this
> issue. Also, if there's a recommended procedure for addressing this issue
> (and others that might arise due to non-native line endings), I'd be
> interested
