On 01.03.2011 18:30, Todd Gleason wrote:
> I’m looking into TortoiseSVN client-side hooks and according to
> http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-settings.html you
> must include the working copy path. It appears that this is just a
> filter used to pick what script to use; if the specified directory is
> part of a working copy, and you commit that directory or a child, then
> the hook gets invoked.
>
> The problem I have is that users may use a particular folder as a
> container for many working copies, and they may rename them and still
> commit from the renamed working copies. In this case I would rather have
> the hook build in the intelligence to know whether it applies to that
> particular working copy, and if so, do its work. Or branch to different
> sets of logic based on what it does find.
>
> Due to this use case, I wonder if we could get support for wildcards of
> some sort in the working copy paths? Being able to say “C:\*” or
> “C:\Foo\*” (or regex matching) would allow us to get more comprehensive
> coverage with scripts.

You can specify the path "C:\Foo" and it will get applied to all working
copies below that path.
I'm using that for a long time now, works just fine.