NOTE this post is SUMMARY, not part of the debate...
On Friday 02 February 2007 15:01, Erik Huelsmann wrote:
> On 2/2/07, Jeff Smith <jsmith@robotronics.com> wrote:
> > On Thursday 01 February 2007 18:17, Duncan Murdoch wrote:
> > [...]
> >
> > > I think it's an absolute
> > > requirement that svn shouldn't change the file content. If the
[...]
> There is one and only one correct internal Normalized Form of files
> with a given svn:eol-style. Not converting brings much more trouble
> on the implementation side than it does when converting. svn needs
> to convert and this has nothing to do with the user.
Although it seemed as if the discussion was a dead end long ago, I
feel obligated to list the summary of facts I found:
[ NOTE: The original question was whether subversion should offer an
option to allow heuristic importing of text files with mixed eol
styles. This is only an issue when setting the svn:eol-style
property.
Recent Origins:
http://svn.haxx.se/users/archive-2007-01/0449.shtml
http://svn.haxx.se/users/archive-2007-01/0720.shtml
http://svn.haxx.se/users/archive-2007-01/0698.shtml
http://svn.haxx.se/users/archive-2005-11/0789.shtml
]
====
* for: It is a very common problem [search archive for "Inconsistent
line ending style"], esp. in source code with diverse contributors,
such as open source projects. Aborting the entire tree when only a
few files were corrupt in this way is much more time consuming.
* for: The option would be optional, and therefore would not
interfere with situations where corruption of binary content is a
concern.
* for: While allowing the option will improve capability, avoiding
this option will not stop binary files from passing the heuristic
test it already depends on, and corrupting some file that was
mistakenly imported with svn:eol-style (i.e. a binary file which
happened to only have \n chars and no \r\n combinations).
====
* wannabe against: The version control system "must not modify
content" before importing. [Aparently this statement needs reworded,
as I verified that Subversion ALREADY modifies text files when
"normalizing", and therefore loses original style of text that was
imported]
* against: If the user imports a binary file using this option (i.e.
mistaken as text and forced to translate) , it will likely become
corrupt in the repository.
* against: A complex mix of eol styles can create an ambiguous number
of blank lines, which could be bad if mis-interpereted for perlpod
docs.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Feb 6 23:56:15 2007