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

Re: Status behaviour

From: Kevin Pilch-Bisson <kevin_at_pilch-bisson.net>
Date: 2001-10-22 20:02:50 CEST

On Mon, Oct 22, 2001 at 12:56:26PM -0500, Ben Collins-Sussman wrote:
> Kevin Pilch-Bisson <kevin@pilch-bisson.net> writes:
> > 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.
> I experience this use-case all the time, actually. I've gotten in the
> habit of running 'svn status -uvn'. I guess this won't show
> unversioned items. But then again, I never really want to see them
> either. :-)
Right. It currently will only work on things that are in the entries file.
The problem comes in when you specifically ask for the status of a file that
is not versioned (most commonly in the wildcard case).

We could have it print the ?, or print nothing. Currently it errors out though
which I don't think we want.

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.

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