On Thu, Nov 15, 2012 at 4:24 PM, Johan Corveleyn <jcorvel_at_gmail.com> wrote:
> On Thu, Nov 15, 2012 at 9:56 PM, Paul Burba <ptburba_at_gmail.com> wrote:
>> On Thu, Nov 15, 2012 at 3:45 PM, Johan Corveleyn <jcorvel_at_gmail.com> wrote:
>>> Does svnlook support inherited-props?
>>> At first sight, I think not
>>> (can't see the --show-inherited-props option in the output of 'svnlook
>>> help propget').
>>> Are there any plans to implement this before 1.8?
>> No plans as of right now, but I can certainly tackle that if necessary.
> I'm not sure, but maybe it would be useful for example in generic
> pre-commit hook scripts for enforcing auto-props:
> for x in (svnlook changed -t $TXN):
> if ($x is addition or propmod):
> autoprops = svnlook pg -t $TXN --show-inherited-props svn:auto-props $x
> enforce_props(autoprops, $x)
> (possibly combined with some authz that makes the
> project-base-directory, containing svn:auto-props, only writable by
> project administrators or something like that)
> But then again, this would probably be a very inefficient way to check
> this. If the commit adds 100 files, it doesn't make much sense to
> propget 100 times the same autoprops from some project-root-dir.
> But I guess in some cases it can still be quite useful, and it doesn't
> hurt to have the option available, does it :-) ?
Yeah, it should be relatively easy to do, I've got time before 1.8
heads out the door, and it can't hurt to have it. So I'll look into
making this happen tomorrow.
Paul T. Burba
CollabNet, Inc. -- www.collab.net -- Enterprise Cloud Development
Received on 2012-11-15 23:54:59 CET