You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by John McGrath <ta...@yahoo.com> on 2007/03/14 19:24:10 UTC

svn status continue on error feature

Hi All,
I'm relatively new to svn - but think it is great. 
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!

I am not on the mailing list yet - please copy me on responses.

Cheers
John



Re: svn status continue on error feature

Posted by Ryan Schmidt <su...@ryandesign.com>.
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  
function


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org