[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: cr, lf on merge ... implement or use gnu diff option?

From: Noel Yap <yap_noel_at_yahoo.com>
Date: 2002-11-12 14:54:58 CET

--- solo turn <soloturn99@yahoo.com> wrote:
> for our users its very simple:
> "if my editor shows a line ending, then its a line
> ending .... why
> svn is so stupid and does not know this? i want my
> visual source safe
> back!"

I don't understand your question. Line endings imply
text files. Are you asking why Subversion can't tell
the difference between text files and binary? Or, are
you requesting that Subversion should tell the

The answer to the former is, "To a computer, there is
no difference between text and binary files; they're
just a bunch of bytes, after all. Categorizing
something as text or binary is done by a person."

I believe Subversion has ample features to handle line
ending woes.

BTW, is VSS available on Unix now?

> and the editors we use treat cr/lf/crlf/lfcr as
> line-ending.

Good, now you just have to check if they're changing
the line endings.

> and we are not introducing cr-lf on unix, so our
> (dummy?) windows
> users can safely receive files from the unix world.

It would be Windows editors that would be (mangling
and) introducing CR/LF; Unix uses one-character line
endings. Also, typically, Unix-origined editors are
aware of line-ending woes so they try their best to
stick to whatever the file is already using. OTOH,
I've seen Windows-based editors not conform to this
convention and assume you want to use CR/LF no matter


Do you Yahoo!?
U2 on LAUNCH - Exclusive greatest hits videos

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Nov 12 14:56:56 2002

This is an archived mail posted to the Subversion Dev mailing list.