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

RE: svn status: filter on file extension

From: Niel De Clerk <NDeclerk_at_Angloplat.com>
Date: Wed, 20 Jan 2010 11:00:10 +0200

Thanks for the reply.

BTW, a good alternative to grep in Windows is findstr

The following works well (to only list *.kb files)

Svn status --verbose --show-updates |findstr /E .kb


-----Original Message-----
From: C. Michael Pilato [mailto:cmpilato_at_collab.net]
Sent: 19 January 2010 16:55
To: Niel De Clerk
Cc: users_at_subversion.apache.org
Subject: Re: svn status: filter on file extension

Niel De Clerk wrote:
> Good Day
> I'd like to know if there is a way to make a SVN STATUS command
> recursive while filtering the files using a wildcard?
> I need this purely for performance reasons. I'm guessing that the
> amount of data that the repository need to pass back (via a rather
> slow
> network) will be less, and also that I'll save time when processing
> the results since I don't have to filter out lots of unneeded

Actually, the amount of data currently passed over the network for 'svn
status -u' is proportional to the amount of *change* in the tree since
the working copy was last updated, not to the size of the tree itself,
and is optimized for directory comparisons as opposed to comparisons of
individual file revisions.h

> However, I'm often only interested in the files with a specific
> extension (*.kb). So I've tried to use
> svn status --verbose --show-updates *.kb
> But this only returns the .kb files found in the current directory
> non-recursive)
> Your assistance will be greatly appreciated.

Yeah, this is pretty much where 'grep' comes into the picture. :-)

C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand
Received on 2010-01-20 10:01:58 CET

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

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