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

Inaccurate "Updated to revision" when updating multiple targets

From: Ryan Schmidt <subversion-2010d_at_ryandesign.com>
Date: Wed, 3 Nov 2010 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.
$

The expected output is:

$ svn up a b c
At revision 2.
A b/something
Updated to revision 2.
At revision 2.
$

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.

The reproduction recipe is:

$ svnadmin create repo
$ REPO=file://$PWD/repo
$ svn mkdir $REPO/{a,b,c} -m x

Committed revision 1.
$ svn co $REPO wc
A wc/a
A wc/b
A wc/c
Checked out revision 1.
$ cd wc
$ svn up a b c
At revision 1.
At revision 1.
At revision 1.
$ svn mkdir $REPO/b/something -m x

Committed revision 2.
$ svn up a b c
At revision 2.
A b/something
Updated to revision 2.
Updated to revision 2.
$ svn up a b c
At revision 2.
At revision 2.
At revision 2.
$
Received on 2010-11-03 10:49:05 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.