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

Status behaviour

From: Kevin Pilch-Bisson <kevin_at_pilch-bisson.net>
Date: 2001-10-22 19:18:48 CEST

Hey all,

Just playing around with svn st today, and I came across a couple of things.

1) With the new code you can't see prop-mods on a dir, without the possiblility
of also seeing all the entries in that dir as well. I can live with this,
just wanted to make sure everyone else can as well.

2) If you run svn status on a non-versioned item, you get an error. That
is what one would expect, except for the following use case. It would be
nice sometimes to run svn status -un *, so that you get a shallow glimpse of
the current directory and its children. The problem is that if * includes
non versioned items, you get an error.

3) If you do svn status -un *, the head revision is reported for each of
the entries in *.

I have made some small changes to clients/cmdline to modify the behaviour
of 2 and 3. Specifically, if multiple targets are passed, svn status prints
'? filename' when it receives ENOENT or SVN_ERR_BAD_FILENAME errors. 2nd,
the status command only prints the head revision on the last target in the
array.

What do people think of these changes?

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Kevin Pilch-Bisson                    http://www.pilch-bisson.net
     "Historically speaking, the presences of wheels in Unix
     has never precluded their reinvention." - Larry Wall
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  • application/pgp-signature attachment: stored
Received on Sat Oct 21 14:36:45 2006

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