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

Re: Inconsistent line ending style terminates add without message

From: David Weintraub <qazwart_at_gmail.com>
Date: Mon, 19 Oct 2009 22:07:51 -0400

On Sun, Oct 18, 2009 at 12:13 PM, johnea <me_at_johnea.net> wrote:

> Regarding the files being omitted from the add, does anyone know if
> this is the expected behavior of svn add, or am I doing something
> wrong here?

Subversion is suppose to be an all or nothing commit. Either all of your
changes are committed or none are.

Unless you have a pre-commit trigger or have auto-properties set to
svn:native, inconsistent line endings shouldn't be a problem. If you have a
pre-commit trigger that requires particular line endings, the commit simply
won't go through and none of your changes will be committed. You'll get an
error message from the pre-commit trigger.

If you have the svn:native property set, and you have inconsistant line
endings, you'll get an error message stating that the commit failed because
of inconsistant line endings, and none of your changes will be committed.

Otherwise, Subversion simply doesn't care about line endings. There is no
difference between a binary or nonbinary file the way Subversion stores
files. We have plenty of files with inconsistant line endings, and
Subversion has no problems with those.

Did all the files get added with the "svn add"? Was there an error message
on the add? I can't say exactly what happened without more information. All
I can say is that a commit either works and all files are committed or
doesn't work and none of the files are committed. That's the way Subversion
was designed.

David Weintraub
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-20 04:08:43 CEST

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