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

Error handling issue during commit

From: devellison <devellison_at_gmail.com>
Date: Fri, 2 May 2008 09:48:19 -0700 (PDT)

   Looked at the issue tracker and did a quick search here but didn't
find a reference to this problem, so...

If you commit multiple files that have not yet been added to the
repository, the error handling does not always report errors to the
user and completion may be reported as successful even if it was not.

Specifically, I have the eol-style:native property set for several
file types. When I attempt to *add* one or multiple files with a non-
native EOL style, I receive an error reporting the mismatch - this is
correct behavior.

However, if I try to *commit* a group of previously unversioned files
and one has a mismatch, it appears to add all of the files *up to the
bad one*, then commit them and report a successful commit. The bad
file and all files (good or bad) after the error are not committed to
the repository, and the user is not warned of this.

I've run into this a couple of times recently migrating a project into
SVN - one time it was obvious (3 files were committed out of a few
hundred), but the other time just 4 files from an entire library were
dropped and I didn't catch the mistake until I committed at a lower
level and saw unversioned files where there should have been none.


To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-05-02 18:54:00 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.