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

Re: [PATCH] New feature: status --filter

From: David Glasser <glasser_at_davidglasser.net>
Date: 2007-10-23 00:42:43 CEST

On 10/22/07, Peter Samuelson <peter@p12n.org> wrote:
> [Eric Gillespie]
> > People do use the svn command line on Windows, and we the
> > Subversion project support that.
> Still, Windows borrows the Unix concept of pipelines through which you
> can filter commands, even if a lot of Windows users are not comfortable
> using this. Windows, indeed, has a 'find' command which is a bit like
> fgrep, and can be used for this purpose ('| find C') if you don't mind
> a few false positives.
> > Moreover, even on Unix,
> >
> > svn st --filter C
> >
> > is clearer than
> >
> > svn st | grep -E '^(C.)|(.C)'
> svn st | egrep ^.?C
> ...but in practice I never expect property conflicts, as I almost
> always commit property changes immediately rather than as part of a
> larger bout of hacking. So, for me:
> svn st | grep ^C
> which seems very clear and concise. I think the proposed syntax for
> covering all the possible options in --filter is in fact _harder_ to
> get right, without RTFMing each time, than grep. Especially if you
> want to support 'grep -v' functionality, which seems useful.

I must admit, on the one hand I wouldn't want this feature to have
arbitrarily complicated syntax, but on the other hand the most common
use I would personally have for it would be a negative filter on '?'.


David Glasser | glasser_at_davidglasser.net | http://www.davidglasser.net/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 23 00:42:54 2007

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.