[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Issue 4070] forced update doesn't correct eols of existing obstructions

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Mon, 28 Nov 2011 14:41:53 -0500

On 11/28/2011 02:19 PM, Daniel Shahaf wrote:
> I can see the rationale for not showing it in status (since it can't be
> committed), but I suppose there is a reason to show it --- namely, that
> if the file has svn:eol-style=LF but the on-disk file has CRLF line
> endings, that might break my build and I'd like the tool to tell me
> about it.
> I'm leaning to +1 on having 'svn status' _optionally_ report files that
> have the wrong eol style on disk.

I would never have assumed that 'svn status' *didn't* report such files.
Have we always had such madness as our default behavior?!

C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

Received on 2011-11-28 20:42:47 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.