You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Se...@fujitsu-siemens.com on 2005/06/03 17:08:32 UTC

RE: [svn] Tutorial: hook scripts and conf files under version control

Eli Barzilay wrote:

> On Jun  3, Brandt, Servatius wrote:
> > Hello,
> > 
> > I've written a tutorial how to put Subversion hook scripts and
> > configuration files under version control.  [...]
> 
> Very nice, thanks.
> 
> One comment, in case you put it somewhere -- an alternative to
> automatic updates on commits is to have you notified about changes.
> It kills the point of being able to update the configuration remotely,
> but I use it for something else: I have a repository for private use
> for people who wants one, so I've put the configuration files in the
> repository and they can edit their own access permissions.  I'm
> getting emails, so I can check their changes and update the actual
> copy if its fine.

This works fine if those persons know how to work on the repository
configuration and your task is just to say "Yep" when you receive the
commit message.  But it would not be more work if the other users just
ask you in a hand-written email to give them the permissions they need
and you change the configuration yourself in the remote copy and get the
update to the real repository configuration files automatically done on
the commit.  But my method is not really better than yours, just more
universal as it doesn't require configuration know how of the other
users.

For a repository for private use, I would give each user all write
permissions for his own part of the tree, but no permission to change
the parts of other users.  So there won't be much need to change the
configuration, except when adding a new user.

I added already a remark about your method to the tutorial, but now
I tend to withdraw it.  I don't want to add too much special cases as
this makes it all harder to understand for beginners.  A more
experienced Subversion user will just take the ideas and adapt them to
his personal needs, anyway.  But thanks a lot for your comments, it's
interesting to see how other people do such things.

- Servatius

------------------------------------------------------------------------
Servatius Brandt             Phone: +49 89 636-41504
Fujitsu Siemens Computers    Fax:   +49 89 636-48716
EP SW AD C++                 Email: Servatius.Brandt@fujitsu-siemens.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org


RE: [svn] Tutorial: hook scripts and conf files under version control

Posted by Eli Barzilay <el...@barzilay.org>.
On Jun  3, Servatius.Brandt@fujitsu-siemens.com wrote:
> 
> For a repository for private use, I would give each user all write
> permissions for his own part of the tree, but no permission to
> change the parts of other users.  So there won't be much need to
> change the configuration, except when adding a new user.

Well, in a university setting, people will want to change these
permissions for new things -- every time you write a paper with
someone else, you'll want to create a new directory and make it
writable by the other author.

-- 
          ((lambda (x) (x x)) (lambda (x) (x x)))          Eli Barzilay:
                  http://www.barzilay.org/                 Maze is Life!

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org