Re: messing with CVS_LOCAL_BRANCH_NUM

2003-08-03 Thread Brian Reichert
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: http://www.scriptkiddie.org/freebsd/setting_up_local_repo.html which makes use of the

Re: messing with CVS_LOCAL_BRANCH_NUM

2003-08-03 Thread John Polstra
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 away your

Re: messing with CVS_LOCAL_BRANCH_NUM

2003-08-02 Thread Simon L. Nielsen
On 2003.08.02 15:35:48 -0400, Brian Reichert wrote: I'm exploring the 'local repository' tactics as described in: http://www.scriptkiddie.org/freebsd/setting_up_local_repo.html [snip] cvs ci src cvs commit: Examining src You are committing on the wrong repository! cvs commit:

Re: messing with CVS_LOCAL_BRANCH_NUM

2003-08-02 Thread Brian Reichert
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: http://www.scriptkiddie.org/freebsd/setting_up_local_repo.html [snip] cvs ci src cvs commit:

Re: messing with CVS_LOCAL_BRANCH_NUM

2003-08-02 Thread Brian Reichert
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 following

Re: messing with CVS_LOCAL_BRANCH_NUM

2003-08-02 Thread John Polstra
In article [EMAIL PROTECTED], Brian Reichert [EMAIL PROTECTED] wrote: I'm exploring the 'local repository' tactics as described in: http://www.scriptkiddie.org/freebsd/setting_up_local_repo.html which makes use of the CVS_LOCAL_BRANCH_NUM evironment variable. [...] Any advice? Yes: