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

Re: Why do commands fail when a file is unknown to svn?

From: John Peacock <jpeacock_at_rowman.com>
Date: 2004-03-04 21:31:16 CET

Nicolás Lichtmaier wrote:

> Besides, SVN doesn't complain when trying to commit an up-to-date
> file... according to you.. shoud that be changed? I think that's a
> similar case.

Not at all; the up-to-date file is already known, but it doesn't need anything
done to it, so this is a guaranteed harmless state. Trying to commit a file
which doesn't already exist in the repository is not always completely harmless.


1) The file _should_ be in the repository, so by erroring out, you can add it
and then commit it along with the other files in this changeset;

2) The file _shouldn't_ be in the repository, in which case your selection of
files on the command line was in error.

Just because you _could_ do something in CVS doesn't make that behavior better;
I suspect this was probably a conscious choice to raise this to an error instead
of a warning (to prevent case #1 above). There are probably a number of things
in CVS which people got used to using due to laziness, rather than it being a
good feature.

That being said, you could request an enhancement to warn on unknown files
(--warn-unknown???) instead of erroring out. It's also quite easy to write a
little script to construct the appropriate commandline.


John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 4 21:30:21 2004

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