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

Re: Command-line output changes in 1.3

From: Daniel Rall <dlr_at_finemaltcoding.com>
Date: 2005-10-12 20:01:15 CEST

On Wed, 12 Oct 2005, kfogel@collab.net wrote:

> Daniel Rall <dlr@finemaltcoding.com> writes:
> > I had a rather strong urge to change 'svn status -u -v' to show the
> > repository state rather than the working copy state (as it does now),
> > but did not make the trivial (from a code perspective) change in 1.3,
> > due to concerns about backwards compatibility. I propose we do consider
> > where such a change belongs: 1.4, 2.0, etc.
>
> I meant to ask, what exactly does this change mean?

'svn help st' shows:

  ...
  Remaining fields are variable width and delimited by spaces:
    The working revision (with -u or -v)
    The last committed revision and last committed author (with -v)
    The working copy path is always the final field, so it can
      include spaces.
  ...
    svn status --show-updates --verbose wc
     M 965 938 kfogel wc/bar.c
           * 965 922 sussman wc/foo.c
    A + 965 687 joe wc/qax.c
                 965 687 joe wc/zig.c
    Status against revision: 981
  ...

Currently, all of the information except for the * is read from the entries
file. As the --show-updates (-u) argument triggers repository access, most
people I've surveyed have been surprised that the "last committed revision"
and "last commited author" information is not any more-up-to-date info from
the repository, but still what's read from the entries file.

Considering the slow-down you get from --show-updates contacting the
repository, the fact that the delta editor always sends back any new state
from the repository, and the fact that we are now finally grabbing this state
(instead of dropping it on the floor like we used to do), actually making use
of that information for 'svn st -uv' would be a great improvement in
behavior.

Though a trivial code change localized to only a couple of files, this is a
rather noticable departure from the current behavior of 'status'.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 12 20:00:38 2005

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

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