David Wilson wrote:
> Hi there,
>
> I have been using Subversion 1.1 for about 3 weeks now, and on the whole
> I've had no surprises. I accidently commited a symlink to a repository,
> which despite not being what I had intended to do, turned out rather
> useful anyway. Ok, so on to my little niggle:
>
> I have a set of working copies stored in ~/www/, a subset of which I
> like to have updated daily by cron. My cron script started failing with
> 1.1:
>
> svn: '/home/dw/www' is not a working copy
>
> The command-line for this looked like:
>
> svn up /home/dw/www/site-a /home/dw/www/site-b /home/dw/www/site-c
>
> With 1.0, svn would treat these as individual working copies and update
> correctly as expected, but with 1.1 it appears that svn is trying to
> optimise the request by finding a common root, and failing to do so.
>
> I would imagine the old (and in my case preferred) svn 1.0 interface
> behaviour should be easy enough to emulate in 1.1. The only question is,
> is this actually a bug? I personally don't see how it can't be classed
> as a UI regression bug.
>
> Thoughts? Please CC: me directly as my -users mailbox isn't read very
> often. :)
I think this is definitely a bug.
Would you like to file it in the issue tracker?
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Dec 14 16:11:41 2004