Re: messing with CVS_LOCAL_BRANCH_NUM

In article <[EMAIL PROTECTED]>, Brian Reichert <[EMAIL PROTECTED]> wrote: > On Sat, Aug 02, 2003 at 03:22:06PM -0700, John Polstra wrote: > > Yes: look for a different approach, or at least backup your local > > repository frequently. There are known bugs in CVSup which can cause > > it to throw

Re: messing with CVS_LOCAL_BRANCH_NUM

On Sat, Aug 02, 2003 at 03:22:06PM -0700, John Polstra wrote: > In article <[EMAIL PROTECTED]>, > Brian Reichert <[EMAIL PROTECTED]> wrote: > > I'm exploring the 'local repository' tactics as described in: > > > > > > > > which m

Re: messing with CVS_LOCAL_BRANCH_NUM

In article <[EMAIL PROTECTED]>, Brian Reichert <[EMAIL PROTECTED]> wrote: > I'm exploring the 'local repository' tactics as described in: > > > > which makes use of the CVS_LOCAL_BRANCH_NUM evironment variable. [...] > Any advice

Re: messing with CVS_LOCAL_BRANCH_NUM

On Sat, Aug 02, 2003 at 04:04:41PM -0400, Brian Reichert wrote: > On Sat, Aug 02, 2003 at 09:49:00PM +0200, Simon L. Nielsen wrote: > > The problem is the file CVSROOT/nocommits.sh, which is used as a > > safeguard in the FreeBSD tree. I replace the file every time I run > > cvsup with the followi

Re: messing with CVS_LOCAL_BRANCH_NUM

On Sat, Aug 02, 2003 at 09:49:00PM +0200, Simon L. Nielsen wrote: > On 2003.08.02 15:35:48 -0400, Brian Reichert wrote: > > > I'm exploring the 'local repository' tactics as described in: > > > > > [snip] > > > cvs ci src > >

Re: messing with CVS_LOCAL_BRANCH_NUM

On 2003.08.02 15:35:48 -0400, Brian Reichert wrote: > I'm exploring the 'local repository' tactics as described in: > > [snip] > > cvs ci src > cvs commit: Examining src > You are committing on the wrong repository! > cvs

messing with CVS_LOCAL_BRANCH_NUM

I'm exploring the 'local repository' tactics as described in: which makes use of the CVS_LOCAL_BRANCH_NUM evironment variable. This is all under 4.7-RELEASE. My general method is: setenv CVS_LOCAL_BRANCH_NUM 1000 setenv MYB