[Top][All Lists]

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

Re: Problems with Attic permissions

From: Noel Yap
Subject: Re: Problems with Attic permissions
Date: Mon, 14 Oct 2002 12:08:49 -0700 (PDT)

--- Anne McCaffrey <address@hidden> wrote:
> No,the files are not added to branch.
> The 'Branch' is MAIN and the CVS tags shows HEAD.

I don't know why "cvs add" would be doing this, then.

Also, how do you prevent users from going into the
repository and removing an archive file that's /not/
in Attic?

> It is the requirement of our project that no single
> developer should remove files(even using cvs remove)
> without consulting others involved and the PM; some
> of
> them have removed files previously which caused a
> lot
> of confusion.So this is the way we chose to enforce
> it.
> Now they will have to go thro' the cvs admin to
> remove
> unwanted files.
> We review the repository regularly so that any
> unwanted files are usually removed before the
> developers feel the need for it.

I understand your situation.

Dealing with it in this way breaks the "one commit per
change" rule.  Might I suggest something like what we
have here:
0. Usually, developers cannot checkin privileged
1. When developers need to check in something that's
privileged, they need to obtain a pardon (basically
granting permission to checkin) from the owner of the
2. Upon checkin, the pardon is revoked thereby
preventing any further checkins from that user until
another pardon is granted.

Doing the above will allow developers to checkin
altogether everything that belongs in one checkin.


Do you Yahoo!?
Faith Hill - Exclusive Performances, Videos & More

reply via email to

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