[prev in list] [next in list] [prev in thread] [next in thread] 

List:       subversion-issues
Subject:    [Issue 4070]  forced update doesn't correct eols of existing
From:       pburba () tigris ! org
Date:       2011-11-28 18:54:12
Message-ID: 20111128185412.AE412540072 () sc157-tigr ! sjc ! collab ! net
[Download RAW message or body]

http://subversion.tigris.org/issues/show_bug.cgi?id=4070



User pburba changed the following:

                What    |Old value                 |New value
================================================================================
                  Status|NEW                       |RESOLVED
--------------------------------------------------------------------------------
              Resolution|                          |INVALID
--------------------------------------------------------------------------------




------- Additional comments from pburba@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.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=463&dsMessageId=2888409

To unsubscribe from this discussion, e-mail: [issues-unsubscribe@subversion.tigris.org].
[prev in list] [next in list] [prev in thread] [next in thread]