On Thu, Dec 13, 2001 at 01:09:38PM -0600, Karl Fogel wrote:
> 3. This is the variation step:
> 3a - The exact bits of the working file are always sent to the
> repository on commit, and the repository (and text-base)
> updated accordingly. This means that alternating commits
> from different platforms would flip-flop the line-ending
> style in the HEAD; on the other hand, it guarantees that
> EOL conversion will never change the data someone thought
> they committed.
+1 for 3a, since most decent editors won't switch all the line endings anyway,
they will either preserve the same style, or preserve the same style except for
> And of course, for files for which there is only one appropriate
> newline style, they will always have that style in the repository
> (because Subversion clients will never change their style, because the
> property won't be set), so they'll be okay whoever checks them out.
> If you retrieve them with some dav client that doesn't honor the
> property, and your platform's editor messes up the newlines, and you
> commit, well, I don't see how any scheme can prevent that.
Not true. A .dsp file is created on windows, checked in. A unix developer
adds a file to the build, and so adds it to the .dsp file. Her (admittedly
stupid) editor either converts all the line endings, or adds the new lines with
LF style endings. We still need a CRLF, CR, LF, etc value for the property.
Kevin Pilch-Bisson http://www.pilch-bisson.net
"Historically speaking, the presences of wheels in Unix
has never precluded their reinvention." - Larry Wall
Received on Sat Oct 21 14:36:53 2006
- application/pgp-signature attachment: stored