From: Noel Yap <[EMAIL PROTECTED]>
Date: Thu, 5 Sep 2002 10:24:29 -0700 (PDT)
This is more a permissioning problem than a locking
problem.
Right.
One way to solve it, as you said, is to use
chmod/setfacl although I would agree that this is the
wrong tool since, in order to perform those
operations, noe would need to own the file and since
archive files are owned by the last person checking it
in, you'd have to be root in order to do this.
Yah. Though in this case, that's actually not too onerous, because
the code in question really is meant to be changing quite rarely. So
having the small set of people who are in charge of keeping it running
manually do that as root is plausible, though not optimal.
An alternative would be to create a commitinfo script.
I don't know the details of such a script, but I
think I've heard others using one and we use one where
I work -- sorry, I don't have time to look at how our
script works (it may even be reliant on a patch we've
installed).
Ah. That has promise.
HTH,
It does. Thanks.
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
