Ryan Schmidt wrote on Wed, Nov 03, 2010 at 04:48:21 -0500:
> Minor bug report in the way Subversion prints output when I'm updating
> multiple targets, some of which have changes and some of which do not.
>
> Imagine I have directories a, b and c, and I ask Subversion to update
> all three, but only b has changes. The output received with Subversion
> 1.6.13 on Mac OS X 10.6.4 is:
>
>
> $ svn up a b c
> At revision 2.
> A b/something
> Updated to revision 2.
> Updated to revision 2.
> $
>
Same with trunk:
% $svn up A mu B
At revision 2.
U mu
Updated to revision 2.
Updated to revision 2.
>
> The expected output is:
>
>
> $ svn up a b c
> At revision 2.
> A b/something
> Updated to revision 2.
> At revision 2.
> $
>
+1
>
> Looking in subversion/svn/notify.c it looks like it prints "Updated
> to" or "At" depending on whether nb->received_some_change, so that
> variable should be reset when moving to a new target.
>
+1.
(Or should the 'received_some_change' logic live in the library (in the
generation of notifications)? I haven't thought much about that.)
>
Bottom line: agreed that there is a bug here. If you (or anyone else)
wants to file an issue or send a patch for that, go ahead. :-)
Received on 2010-11-03 14:19:29 CET