[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: Julian Foad <julianfoad_at_btopenworld.com>
Date: 2005-02-28 00:12:49 CET

> John Szakmeister <john@szakmeister.net> writes:
>> [Should "export"] error out on targets that are either unversioned, or
>> don't exist (whereas we just silently skipped over them before)

kfogel@collab.net wrote:
> 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.

While you're at it, am I sane in wanting "svn status blah" to return some error
or status code when "blah" is both unversioned and not on the disk? (It is
silent, which implies to me that "blah" is versioned and present and unmodified.)

- Julian

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Feb 28 00:13:59 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.