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

Re: Causing export to fail on nonexistant or unversioned targets.

From: <kfogel_at_collab.net>
Date: 2005-02-27 21:02:24 CET

John Szakmeister <john@szakmeister.net> writes:
> r13151 made the export code stop walking the working copy area, and start
> using the administrative information instead to do the export. With
> that, we can no error out on targets that are either unversioned, or
> don't exist (whereas we just silently skipped over them before). My
> question to the community is should we do that? Right now, if you try
> export a bogus directory (i.e., 'svn export /path/to/wc/bogus-dir'), it
> simply comes back and says it was successful. I think it should return
> an error ('bogus-dir' is unversioned or doesn't exist). I believe this
> would be a change to the way the command line tool works, so I held back
> making that change until we reached a consensus about whether or not it
> was a 'bug' that needed to be fixed.

IMHO, we can consider it a bug when we fail to error on an explicitly
named target that we cannot meaningfully process. So your proposed
change (to return an error saying that bogus-dir is unversioned or
doesn't exist) seems right, and doesn't raise any compatibility
concerns in my mind at least.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Feb 27 21:20:37 2005

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

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