[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How to lock CVS for check-in

From: Greg A. Woods
Subject: Re: How to lock CVS for check-in
Date: Fri, 12 Oct 2001 13:11:51 -0400 (EDT)

[ On , October 12, 2001 at 11:30:07 (-0400), Jake Colman wrote: ]
> Subject: Re: How to lock CVS for check-in
> So please explain how you would prevent access to specific branches for
> specific users?  I'm not sure why you think that this is not a reasonable
> thing to want to try to do?

Simply put, I wouldn't.

Provided you trust each other (you should if you're working on the same
project), and provided everyone keeps an eye on everyone else looking
for not just illicit use, but also simple mistakes and such, there's no
real need for branch locking.

I see accidental commits to the wrong branches in all kinds of projects,
but they never cause any problems and they're easily reverted.  People
usually learn from their mistakes, and sometimes they even learn from
the mistakes of other, hopefully learning to be more careful, which is
generally a good thing.

The only time I could possibly see any real need for branch locking
would be in a scenario where people who are more naturally adversaries
are working on separate branches.  However even in this case if a third
independent party is responsible for doing merges, etc., then the
project will still be very much self-policing.

The problem with controls of any kind (locking, access controls, etc.)
is that they can get in the way more than they benefit.  In scenarios
where there are much more powerful mitigating forces they become only a
burden on everyone, not the least of which are the people who have to
set them up and maintain them.

                                                        Greg A. Woods

+1 416 218-0098      VE3TCP      <address@hidden>     <address@hidden>
Planix, Inc. <address@hidden>;   Secrets of the Weird <address@hidden>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]