On Tue, 2006-10-10 at 05:46, Duncan Murdoch wrote:
> >
> >> My editor used to default to CR-LF style text files, and that caused
> >> occasional problems for the Unix users when I committed the wrong EOLs,
> >> but I've got it set to use Unix style all the time now, and it's just an
> >> easier way to live.
> >
> > That's fine as long as you can dictate that everyone involved has to
> > use the same tools. What happens when you have to share text files
> > with someone who has made the opposite choice?
>
> Obviously then one of us will have to worry about conversion, and it'll
> be error prone. However, it isn't really a big problem, in that a smart
> editor will usually get the EOL style right by looking at a file: it's
> only new files that are likely to be wrong. So you need to be careful
> to agree on standards at the beginning of the conversation, and keep an
> eye out for mistakes.
>
> It's not exactly a unique problem. It's just the same thing with word
> processor files: I receive .doc, .wpd, .odf, and .rtf, and it's a bit
> of a pain when I get one that I don't use a lot, but I think it would be
> a lot worse if the communications channel tried to do automatic
> conversions for me.
The problem is that if you were pretending that a text file
was a binary file in your source control system, once anyone
else has treated it in this normal manner for some choice of
OS other than your own, every line becomes changed. While
you are correct about that happening with real binary files,
it doesn't have to happen to text if you treat it as text.
That is, you can cooperate with peers making different
choices and still be able to track changes.
--
Les Mikesell
lesmikesell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Oct 10 14:53:34 2006