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

Re: svn status continue on error feature

From: Ryan Schmidt <subversion-2007a_at_ryandesign.com>
Date: 2007-03-14 22:16:29 CET

On Mar 14, 2007, at 14:24, John McGrath wrote:

> Right now, I'm writing some wrapper scripts, to help users use svn
> in a way they are more familiar with.
> Originally I used to have multiple calls to svn status for each
> file passed to the script, which worked fine but was slow, as the
> repository may be remote.
> I then tried the method of calling svn status file1 file2 file3 etc.
> However, if any of the files are not in the repository, svn will
> error out, and then stop. I would like it to continue to produce a
> single line of status for each file - i.e. continue on error.
> Because of this "feature" I am unable to use svn status with
> multiple files. Any workarounds or info is greatly appreciated!

svn status or svn status --show-updates? The former should not access
the repository, and therefore should not be slow even if the
repository is remote, whereas the latter does access the repo and so
could be affected by network latency and bandwidth.

Can you not just call "svn status" (or "svn status --show-updates")
without any arguments? Won't that show you the status of everything
in your working copy?

To reply to the mailing list, please use your mailer's Reply To All  
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Mar 14 22:16:55 2007

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

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