kfogel@tigris.org writes:
> Modified: trunk/subversion/clients/cmdline/status.c
> ==============================================================================
> --- OLD/trunk/subversion/clients/cmdline/status.c Thu Jan 10 21:41:58 2002
> +++ NEW/trunk/subversion/clients/cmdline/status.c Thu Jan 10 21:41:58 2002
> @@ -216,10 +216,15 @@
> if ((skip_unrecognized) && (! status->entry))
> continue;
>
> - if (detailed)
> - print_long_format (path, status);
> - else
> - print_short_format (path, status);
> + if (status->text_status != svn_wc_status_none)
> + {
> + if (detailed)
> + print_long_format (path, status);
> + else
> + print_short_format (path, status);
> + }
> + else
> + printf (">>> \"%s\" does not exist <<<\n", path);
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?
--
Philip
---------------------------------------------------------------------
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