Philip Martin <philip@codematters.co.uk> writes:
> This "does not exist" message gets printed for files that get added to
> the repository. My current working copy is rev 861 and I get
>
> $ 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?
Yes, this is a bug -- you're right about the intended behavior.
I've annotated and reopened the original issue, and in the meantime
reverted the code, since the buggy behavior is worse than the benefit
the change brings when operating correctly.
Thanks for mentioning it!
Joseph Dane, want to take another look at this?
-Karl
---------------------------------------------------------------------
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