Hi wizards. I have what I believe to be a different variant of the
perpetual question about locking. I have a situation where, due to
persistent problems with some hackers modifying some parts of a code
base without understanding it first, we end up with broken code much
more frequently than is
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 sinc
From: [EMAIL PROTECTED]
Date: Thu, 5 Sep 2002 13:03:59 -0500 (CDT)
[...]
> Set up a Unix group which has write access to the repository.
> Ensure that everything in the repository is read-only to everyone
> else, and ensure that the directories all have the setuid bit
This is more a permissioning problem than a locking
problem.
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 perso
On Thu, 5 Sep 2002 [EMAIL PROTECTED] wrote:
> Date: Thu, 5 Sep 2002 13:10:51 -0400
> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: [info-cvs] More locking, sort of
>
> Hi wizards. I have what I believe to be a different variant of the
> perpetual question abo
> On Thu, 5 Sep 2002 [EMAIL PROTECTED] wrote:
>
> > Date: Thu, 5 Sep 2002 13:10:51 -0400
> > From: [EMAIL PROTECTED]
> > To: [EMAIL PROTECTED]
> > Subject: [info-cvs] More locking, sort of
> >
> > Obviously, there are political problems at work here; i
[ On Thursday, September 5, 2002 at 13:10:51 (-0400), [EMAIL PROTECTED] wrote: ]
> Subject: More locking, sort of
>
> Hi wizards. I have what I believe to be a different variant of the
> perpetual question about locking. I have a situation where, due to
> persistent problems wi
Greg A. Woods wrote:
> [ ... ]
> Automated regression testing of the baseline on every commit ensures
> other developers always have correct code to work with.
>
> One such tool with these features is Aegis.
>
> http://www.canb.auug.org.au/~millerp/aegis.html
>
> They can be hacked onto C
[ On Saturday, September 7, 2002 at 00:21:25 (+1000), Matthew Hannigan wrote: ]
> Subject: Re: More locking, sort of
>
> Greg A. Woods wrote:
> > [ ... ]
> > Automated regression testing of the baseline on every commit ensures
> > other developers always hav
Greg A. Woods wrote:
> [ On Saturday, September 7, 2002 at 00:21:25 (+1000), Matthew Hannigan wrote: ]
>>Have you or do you know of anyone who has jumped
>>from CVS to Aegis?
>
>
> I don't know about "jumped", but I have used it on one new project and
> will probably use it on other new multi-pe
Thanks for your reply, I agreed with most of
it.
Greg A. Woods wrote:
> Finally note that not everyone will need the kind of control that Aegis
> offers -- for many people CVS is sufficient.
I think this is the biggy; there seems to a lot of learning
to do in adopting Aegis, compared to cvs, es
11 matches
Mail list logo
