On 4 August 2011 01:59, David Weintraub wrote:
> ...
> SNIP
> ...
> I have what I call my Kitchen Sink pre-commit trigger that does all
> sorts of stuff. One of the tasks it can do is "ban" files based upon
> their name (either regular expression or Ant glob). If a user adds a
> file with a forbid
On 3 August 2011 05:47, Nico Kadel-Garcia wrote:
> That's what "svn checkout" for initial setup, and "svn update" or "svn
> revert" of the local copy are for.
We already have that working, I just outlined the current setup:
http://files.foobar.org/ is a direct file mirror (less revision
control;
On 3 August 2011 04:37, David Weintraub wrote:
> NO! NO! NO! AUUUGGGHHH!
>
> Never update a repository with a hook.! That's why you're given the
> relatively safe "svnlook" command. It allows you to look, but not
> touch a repository.
> ...
> SNIP
> ...
Arrrgghhh damn it! Exactly what I feared. E
Hi list
I've been stumped by this issue for months. I had never enough time to
troubleshoot it, so I'm finally desperate after having spent an entire
day trying to figure things out.
We have a _local_ checkout of the repository on our server, and our
post-commit hook needs to run svn-add, svn-rm
Hi all
I have something like the following:
[groups]
admin = joe
contrib = susan, mark
devs = andy, jane
[/]
* = r
[/trunk]
@admin = rw
[/trunk/contrib]
@contrib = rw
@devs = rw
[/trunk/dev]
* =
@contrib =
@devs = rw
Unfortunately, authentication does not work, and anyone can read
'/trunk/de