From: David Everly [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 12, 2001 5:03 PM
cvs -n stat filename seems only to work from a 'sandbox' point of
view. How would I use that in the context of a commitinfo script?
In local mode, the commands in commitinfo have direct access to your
GAW == Greg A Woods [EMAIL PROTECTED] writes:
GAW Far worse are operations which add, delete, or move, tags; but as
GAW I've mentioned several times again recently it would be very easy to
GAW add an additional access control for those kinds of things, at least
GAW on a
[ 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
[ On Thursday, October 11, 2001 at 11:11:21 (+0530), Shubhabrata Sengupta wrote: ]
Subject: Re: How to lock CVS for check-in
At least in pserver access it is and I think it is also available in for
local repository access as well. I am not sure about :ext: access though.
I agree that its
PROTECTED]]
Sent: Thursday, October 11, 2001 9:58 AM
To: CVS-II Discussion Mailing List
Subject: Re: How to lock CVS for check-in
[ On Thursday, October 11, 2001 at 11:11:21 (+0530), Shubhabrata Sengupta
wrote: ]
Subject: Re: How to lock CVS for check-in
At least in pserver access it is and I think
GAW == Greg A Woods [EMAIL PROTECTED] writes:
GAW [ On Thursday, October 11, 2001 at 08:24:11 (+0530), Shubhabrata
GAW Sengupta wrote: ]
Subject: Re: How to lock CVS for check-in
Wondering why this enhancement is needed in the commitinfo interface
when you can always
[ On , October 11, 2001 at 14:41:17 (-0400), Jake Colman wrote: ]
Subject: Re: How to lock CVS for check-in
So what do _you_ recommend for implementing branch locking?
I don't recommend implementing branch locking in CVS at all.
Anyone who thinks they need it probably has far larger problems
[EMAIL PROTECTED] (Greg A. Woods) writes:
[ On , October 11, 2001 at 14:41:17 (-0400), Jake Colman wrote: ]
Subject: Re: How to lock CVS for check-in
So what do _you_ recommend for implementing branch locking?
I don't recommend implementing branch locking in CVS at all.
Anyone who
] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 11, 2001 1:46 PM
To: Jake Colman
Cc: [EMAIL PROTECTED]
Subject: Re: How to lock CVS for check-in
[ On , October 11, 2001 at 14:41:17 (-0400), Jake Colman wrote: ]
Subject: Re: How to lock CVS for check-in
So what do _you_ recommend
[ On , October 11, 2001 at 22:27:38 (+0100), James Youngman wrote: ]
Subject: Re: How to lock CVS for check-in
Speaking as someone who recently came very close to having to use cvs
co -p to undo someone else's mistake (they were workign on the wrong
branch by mistake) I disagree
[ On Thursday, October 11, 2001 at 15:14:47 (-0700), Pyatt, Scott wrote: ]
Subject: RE: How to lock CVS for check-in
I don't know your environment, but branch locking is a common mechanism
for allowing read-only access to a branch.
Wel, DUH! :-)
It's really quite useful
and given
to
accept such patches.
Thanks
Shubho
-Original Message-
From: Greg A. Woods [EMAIL PROTECTED]
To: CVS-II Discussion Mailing List [EMAIL PROTECTED]
Date: Thursday, October 11, 2001 10:38 PM
Subject: Re: How to lock CVS for check-in
[ On Thursday, October 11, 2001 at 11:11:21 (+0530
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 10, 2001 10:11 PM
[ On Thursday, October 11, 2001 at 08:24:11 (+0530),
Shubhabrata Sengupta wrote: ]
Wondering why this enhancement is needed in the commitinfo
interface when
you can always get the branch
-Original Message-
From: Brad L. Chisholm [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 10, 2001 1:15 PM
To: David Everly
Cc: Brad L. Chisholm; Larry Jones; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: How to lock CVS for check-in
You can selectively lock branches, but only
]; [EMAIL PROTECTED]
[EMAIL PROTECTED]; [EMAIL PROTECTED] [EMAIL PROTECTED]
Date: Thursday, October 11, 2001 9:07 AM
Subject: RE: How to lock CVS for check-in
Is CVS/Entries available to the commitinfo script when the repository is on
a Unix server and the developer is working on an NT client (pserver
[ On Thursday, October 11, 2001 at 08:24:11 (+0530), Shubhabrata Sengupta wrote: ]
Subject: Re: How to lock CVS for check-in
Wondering why this enhancement is needed in the commitinfo interface when
you can always get the branch information out of the CVS/Entries file which
is always
[EMAIL PROTECTED]
Date: Thursday, October 11, 2001 10:47 AM
Subject: Re: How to lock CVS for check-in
[ On Thursday, October 11, 2001 at 08:24:11 (+0530), Shubhabrata Sengupta
wrote: ]
Subject: Re: How to lock CVS for check-in
Wondering why this enhancement is needed in the commitinfo interface
17 matches
Mail list logo
