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

Re: Fwd: [patch] contrib: support for a 'svn-clean:ignore' dirprop

From: Simon Perreault <simon.perreault_at_viagenie.ca>
Date: Thu, 8 May 2008 16:47:02 -0400

On Thursday 08 May 2008 16:34:26 you wrote:
> Daniel Shahaf reminded me that I should have CC'd you on this mail to
> dev_at_subversion.tigris.org. So if you didn't see this message there ...
> well, here it is.

Thanks. I'm not subscribed to that mailing list so keep me CC'd.

> I love the svn-clean script, I use it _all_ the time.

I'm glad that you like it!

> But I'm on a
> project now where we can run our code from a checkout tree, but to do
> so requires a config file in the tree. This file is unversioned,
> because it is specific to the checkout, but I don't want svn-clean to
> ever remove it.
>
> So this patch implements support for a 'svn-clean:ignore' dir prop,
> which contains glob patterns (one per line), indicating files not to be
> removed even if they are unversioned. I hope people find it useful; my
> coworkers and I certainly do.

Wouldn't it be simpler to just use the svn:ignore property and then add a flag
to svn-clean so that it handles those differently?

Like the git-clean -x flag?

       -x
           Donīt use the ignore rules. This allows removing all untracked
           files, including build products. This can be used (possibly in
           conjunction with git-reset(1)) to create a pristine working
           directory to test a clean build.

In that case the default behavior is to not clean ignored files. svn-clean
does the contrary, so the added flag would make svn-clean not delete ignored
files.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-05-08 22:57:31 CEST

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.