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

Re: auto-props on the server?

From: <kmradke_at_rockwellcollins.com>
Date: Wed, 27 Aug 2008 11:33:25 -0500

Blair Zajac <blair_at_orcaware.com> wrote on 08/22/2008 05:29:10 PM:
> Klaus Umbach wrote:
> >
> > > You only have to do it once per user. It's not elegant, but how
> > many users
> > > could you have converted in the time it took you to write this
> > mail..? But
> > > well, that's your decision. :)
> >
> >
> > It's hard enough to force them to use Subversion instead of a
> > Group-Fileshare...
> >
> >
> >
> > As I am using several repositories with different auto-props
rules, I
> > think the current solution is far from ideal.
> >
> >
> > I was playing around with apache-settings and mod_mime
> > (ModMimeUsePathInfo on), but that didn't help either...
> Not exactly what you're looking for, but you can use this:
> on a working copy to apply all the missing properties and then commit
them. You
> could do this via a cron.

Also not exactly what you are looking for, but I wrote a python
post-commit hook script (or can be run from cron or the command
line) to automatically add any missing svn:needs-lock properties
as a new commit. It uses direct access to the repository, so a
working copy is not needed. This process will confuse some
users, because their working copy version will become instantly
out of date if they commit a file without the correct properties.


Obviously it would need to be rewritten to handle arbitrary auto props
to be useful for the original poster...

Kevin R.
Received on 2008-08-27 18:33:52 CEST

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.