[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: Daniel Shahaf <danielsh_at_elego.de>
Date: Mon, 28 Nov 2011 21:19:19 +0200

pburba_at_tigris.org wrote on Mon, Nov 28, 2011 at 10:54:12 -0800:
> http://subversion.tigris.org/issues/show_bug.cgi?id=4070
> User pburba changed the following:
> What |Old value |New value
> ================================================================================
> --------------------------------------------------------------------------------
> Resolution| |INVALID
> --------------------------------------------------------------------------------
> ------- Additional comments from pburba_at_tigris.org Mon Nov 28 10:54:12 -0800 2011 -------
> Gah, you are quite right Mike. What threw me was that the eol "local mod"
> doesn't show up in status or diff, but that has nothing to do with --force and
> holds true if we simply modify (only) the line endings of any working copy file
> with svn:eol-style set. Uncertain if that is intentional or not, but this issue
> is certainly invalid.

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.


> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=463&dsMessageId=2888409
> To unsubscribe from this discussion, e-mail: [issues-unsubscribe_at_subversion.tigris.org].
Received on 2011-11-28 20:20:10 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.