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

Re: SVN improvements - again ;)

From: Julian Foad <julianfoad_at_btopenworld.com>
Date: 2006-04-06 14:42:41 CEST

Ben Collins-Sussman wrote:
> On 3/28/06, Alexander Limi <limi@plone.org> wrote:
[...]
>> 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...

As an incremental improvement, printing the name of each target would help in
cases like this, but I don't think that gain is worth the risk of upsetting
people who parse the output for the "Updated to revision N." line.

If "svn update" is to handle multiple targets in a better way than just
iterating over them as it does now, then ultimately I'd like it to combine them
and do a single update covering all of them, at least a single update for each
group of targets that are in the same repository. (Whether that would involve
changing the semantics in any way beyond just printing a single "Updated" line
for each repository is unclear.)

The difficulty above, of not knowing which target each part of the output
refers to, can be resolved easily by replacing "svn up *" with something like
"for T in *; do echo Updating $T:; svn up $T; done".

- Julian

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

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.