Hi
I need to lock a Branch, so that no one can check out or check in some
information into it.
I don't have access to the CVS host machine, but I am connecting it
through the CVS Binaries
Please help me out with that.
Thanks
SARAVANAN SUBRMANIAN
SCM
Centrex Mate
SUBRAMANIAN, SARAVANAN (SBCSI) wrote:
Hi
I need to lock a Branch, so that no one can check out or check in some
information into it.
First of all, do you really need to lock the branch? Can you not trust
your developers?
I don't have access to the CVS host machine, but I am connecting it
a tag to identify the files for a release instead
of locking the branch. But if you still must be able to lock the branch,
for whatever reason, you can implement a pre-commit check in commitinfo to
do that.
Simply write a program or a script that determines whether to allow commits
and have
I have a requirement to lock a branch just before the release. I tried to
browse thru the documentation and did get some idea.
Has someone implemented it?
If so could you please share the details?
Thanx
Vijay
___
Info-cvs mailing list
Vijay SP wrote:
I have a requirement to lock a branch just before the
release. I tried to
browse thru the documentation and did get some idea.
Has someone implemented it?
If so could you please share the details?
Get rid of the requirement.
There is never any reason whatsoever for locking
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vijay SP. [EMAIL PROTECTED] writes:
I have a requirement to lock a branch just before the release. I tried
to browse thru the documentation and did get some idea.
Has someone implemented it?
You can do this with the contrib/cvs_acls file.
Add
On Mon, Aug 26, 2002 at 02:44:24PM -0700, Kaz Kylheku wrote:
On Mon, 26 Aug 2002, Pat Young wrote:
Date: Mon, 26 Aug 2002 14:12:04 -0700 (PDT)
From: Pat Young [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [info-cvs] Locking a branch
What is the best way to lock a branch
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
Douglas Finkle writes:
Some time ago John Cavanaugh wrote a patch for commit.c,
bit I don't think it was ever incorporated-- don't know why.
As John himself noted, the patch is not ready for prime time -- it does
not include documentation updates and it is not upward compatible. In
Some time ago John Cavanaugh wrote a patch for commit.c,
but I don't think it was ever incorporated-- don't know why.
As John himself noted, the patch is not ready for prime time
-- it does
not include documentation updates and it is not upward compatible. In
addition, I haven't
Douglas Finkle writes:
Some time ago John Cavanaugh wrote a patch for commit.c,
but I don't think it was ever incorporated-- don't know why.
Perhaps since this patch is more than 3 years old it could be time
to revisit this? (ground swell beginning now ;-)
I do not see a strong
What is the best way to lock a branch? Should I use
the admin -l option? I tried this and couldn't get it
to work. I have also seen some previous post
suggesting to create a #commitinfo file. We would
like to be able to lock a complete branch, so that
developers can not accidentally commit
On Mon, 26 Aug 2002, Pat Young wrote:
Date: Mon, 26 Aug 2002 14:12:04 -0700 (PDT)
From: Pat Young [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [info-cvs] Locking a branch
What is the best way to lock a branch? Should I use
How about:
``Please don't commit to this branch until told
--- Forwarded mail from [EMAIL PROTECTED]
On Mon, 26 Aug 2002, Pat Young wrote:
Date: Mon, 26 Aug 2002 14:12:04 -0700 (PDT)
From: Pat Young [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [info-cvs] Locking a branch
What is the best way to lock a branch? Should I use
How about
On Mon, 26 Aug 2002, Paul Sander wrote:
Date: Mon, 26 Aug 2002 14:12:04 -0700 (PDT)
From: Pat Young [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [info-cvs] Locking a branch
What is the best way to lock a branch? Should I use
How about:
``Please don't commit to this branch
--- Forwarded mail from [EMAIL PROTECTED]
On Mon, 26 Aug 2002, Paul Sander wrote:
Date: Mon, 26 Aug 2002 14:12:04 -0700 (PDT)
From: Pat Young [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [info-cvs] Locking a branch
What is the best way to lock a branch? Should I use
How
16 matches
Mail list logo
