Re: SVN improvements - again ;)

(redirected to the SVN dev list at the request of Ben)

On 3/28/06, Alexander Limi <limi@plone.org> wrote:
> If you want me to not send you these small questions but put it in an
> issue tracker instead, feel free to tell me so.

Oh, I certainly don't mind! But you're likely to get a bunch of more
interesting responses/viewpoints if you mail the
dev@subversion.tigris.org list. :-)

> Just a tiny suggestion for improvement that I assume wouldn't be hard to
> add:
>
> When I do:
>
> $ svn up *
> Updated to revision 21411.
> Updated to revision 66241.
> Updated to revision 21411.
> Updated to revision 21411.
> Updated to revision 66241.
> Updated to revision 66241.
> svn: REPORT request failed on '/svn/collective/!svn/vcc/default'
> svn: Cannot replace a directory from within
>
> It's impossible for me to know where this failed. Would it be possible to
> make it do something like:
>
> $ svn up *
> Archetypes: Updated to revision 21411.
> CMFPlone: Updated to revision 66241.
> Ploneboard: Updated to revision 21411.

Hmm, interesting. Technically, you typed the equivalent of

     $ svn up archetypes cmfplone ploneboard

Which subversion treats exactly the same as if you had typed

     $ svn up archetypes
     $ svn up cmfplone
     $ svn up ploneboard

So yeah, perhaps if 'update' has multiple targets, it can tell you
what it's updating...

See what the folks on dev@ think, too.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Apr 6 13:14:23 2006