[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Locking a branch
From: |
Douglas Finkle |
Subject: |
RE: Locking a branch |
Date: |
Tue, 27 Aug 2002 09:02:14 -0400 |
> >> >> What is the best way to lock a branch? Should I use
> >>
> >> >How about:
> >>
> >> >``Please don't commit to this branch until told otherwise, or you
> >> >will be fired on grounds of inability to follow instructions.''
> >>
> >> >Why work with people that require a piece of software to
> stop them from
> >> >doing what they aren't supposed to?
> >>
> >> Everybody makes mistakes. Good tools warn people when
> they're about to
> >> do something bad.
>
> >How can the computer tell that what you are committing is okay or not
> >for the given branch?
>
> >One way is to require the commit message to have a certain format,
> >like to include 'Bug number: <integer>'.
>
> Another is to match your user ID with a list of users
> permitted to commit
> on a particular branch. Such a list would also have the notion of
> "everyone" and "no one" and perhaps some notion of group membership
> to give better control and easier maintenance.
Paul, thanks for your insight here, and for adding the voice of reason
to this thread. I've also been thinking of implementing locks on a
user id basis. Some time ago John Cavanaugh wrote a patch for commit.c,
bit I don't think it was ever incorporated-- don't know why.
Here it is: http://www.cvshome.org/dev/patches/commitinfo Any thoughts?