Philip Martin writes:
> Branko ,ADŒ(Bibej <brane@xbc.nu> writes:
> > The intent of svn:eol-style was to get coherent results (diffs, that
> > is) when people use all those editors out there that can't preserve
> > the eol style.
Well, I don't know about everyone else, but I've passed the '-w' flag to
diff so often that I now type it without even thinking. That way I never
have to care about what broken editor (or broken source) I'm using at
the moment.
> You say "all those editors", are there lots of them? I find it hard
> to imagine using such a tool. Do they change anything else? Spaces
> to tabs, say, or trailing whitespace?
I've found that shareware Windows text editors are the big
offenders. However, in some cases the whitespace munging (not eol
conversion) is intentional. My default emacs setup uses whitespace mode
to auto-cleanup all whitespace issues. Pretty much every file in the
subversion source tree has trailing whitespace after one or more
lines. So I always have to use the '-w' flag for diff before sending in
patches.
I'd happily fix all of the whitespace issues in the subversion tree in
one giant whitespace cleanup commit but every subsequent commit would
just add more trailing whitespace (because of the brain-dead editors
that *don't* fix whitespace in source code) so its rather pointless.
> Do we have any real-life examples where svn:eol-style fixes a problem?
> Why should it be Subversion's job to solve this problem anyway?
I have often wondered that myself.
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 12 21:21:22 2003