> 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
To recap, I'm looking to a way to lock branches so that people don't
accidentaly check out or commit to an 'inactive' branch. I also need
the solution to work for those accessing CVSROOT vi the :ext: method.
cvs -n stat filename seems only to work from a 'sandbox' point of
view. How would I use
[ 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
> "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> o
> 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 bra
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
[ 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!" :-)
> I
[ 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
>
-Original Message-
From: [EMAIL PROTECTED] [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
[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 implement
[ 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
>>>>> "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
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
[ 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.
>
g List <[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 enhanc
[ 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
EMAIL PROTECTED]>
Cc: Larry Jones <[EMAIL PROTECTED]>; [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 repo
Scott
-Original Message-
From: Shubhabrata Sengupta [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 10, 2001 7:54 PM
To: Pyatt, Scott; 'Brad L. Chisholm'; David Everly
Cc: Larry Jones; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: How to lock CVS for check-in
Won
#x27;Brad L. Chisholm' <[EMAIL PROTECTED]>; David Everly
<[EMAIL PROTECTED]>
Cc: Larry Jones <[EMAIL PROTECTED]>; [EMAIL PROTECTED]
<[EMAIL PROTECTED]>; [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Thursday, October 11, 2001 3:36 AM
Subject: RE: How to lock CVS for check-i
ks,
-Scott
-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, b
You can selectively lock branches, but only if the branch info can get
passed to your commitinfo script. We have "enhanced" the commitinfo
interface locally to send additional parameters we find useful, including
the branch info. I'd be happy to send the diffs (commit.c), if anyone
is intereste
21 matches
Mail list logo
