Re: svn commit: rev 821 - trunk/subversion/include trunk/subversion/clients/cmdline

Philip Martin <philip@codematters.co.uk> writes:

> $ svn st -u ../svn
> M * 861 ../svn/build.conf
> _ * 861 ../svn/subversion/libsvn_ra_dav/fetch.c
> __ * 861 ../svn/subversion/tests/clients/cmdline
> _ * 861 ../svn/subversion/tests/clients/cmdline/diff_tests.py
> >>> "../svn/subversion/tests/clients/cmdline/stat_tests.py" does not exist
> A 0 ../svn/subversion/tests/libsvn_subr/lcs-diff-test.c
> Head revision: 863
>
> We spent days discussing what the svn status command should do, but I
> don't remember this "does not exist" message or the non-standard
> format. Shouldn't this message be restricted to files I explicitly put
> on the command line? This is a bug isn't it?

Yeah, this is a bug. I was about to report it to the list, but then I
thought, "maybe I should read my 46 subversion mails first". :-)

The old behavior for printing "files that will be added if you update"
was just a single asterisk and no local revision number:

_ * ./file-to-be-added

It's nice, because when looking at the local revision column, the
files to be added show up as spatial 'breaks'.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:56 2006