of the CVS_LOCAL_BRANCH_NUM evironment variable.
[...]
Any advice?
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 local branch under certain circumstances. I
won't have time to fix those
local branch under certain circumstances. I
won't have time to fix those issues any time soon. So my advice is,
don't use the CVS_LOCAL_BRANCH_NUM feature.
Darn. :/
[...]
So, can the 'certain circumstances' be described, so that I might
avoid them? Or is that just due to inherent
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.
This is all under 4.7-RELEASE.
My general method is:
setenv CVS_LOCAL_BRANCH_NUM 1000
setenv
the CVS_LOCAL_BRANCH_NUM use,
but unfortunatly there are only 24 hours in a day, so I have no idea
when I will get around to finishing it.
--
Simon L. Nielsen
FreeBSD Documentation Team
pgp0.pgp
Description: PGP signature
no hits...
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 version:
Cool! Thanks for the pointer. Off I go...
I have started some work on documenting the CVS_LOCAL_BRANCH_NUM use
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
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
On Tue, Dec 10, 2002 at 11:56:26AM -0800, Lamont Granquist wrote:
On Tue, 10 Dec 2002, Dmitry Morozovsky wrote:
On Tue, 10 Dec 2002, Lamont Granquist wrote:
LG From the man page, I'm not really sure where it makes a difference other
LG than when someone is playing with IFS, but $@ seems
On Wed, Dec 11, 2002 at 10:59:55AM +0200, Peter Pentchev wrote:
On Tue, Dec 10, 2002 at 11:56:26AM -0800, Lamont Granquist wrote:
On Tue, 10 Dec 2002, Dmitry Morozovsky wrote:
Please note quotes explicitly, $@ is really needed where your parameters
contain spaces (bad practice in
On Wed, Dec 11, 2002 at 10:40:04AM +0100, Stijn Hoop wrote:
On Wed, Dec 11, 2002 at 10:59:55AM +0200, Peter Pentchev wrote:
On Tue, Dec 10, 2002 at 11:56:26AM -0800, Lamont Granquist wrote:
On Tue, 10 Dec 2002, Dmitry Morozovsky wrote:
Please note quotes explicitly, $@ is really needed
On Mon, 9 Dec 2002, Lamont Granquist wrote:
LG I finally figured this out. To use CVS_LOCAL_BRANCH_NUM with a cvs
LG pserver you need to have the environment variable set server-side. That
LG means something like invoking a wrapper from inetd which sets the
LG environment variable and the calls
From the man page, I'm not really sure where it makes a difference other
than when someone is playing with IFS, but $@ seems to be more of what I
intended...
And in case anyone is still reading this now, I'd like to throw out the
suggestion that CVS_LOCAL_BRANCH_NUM should really be an option
spaces (bad practice in filenames, yeah, but don't make yourself
another one PITA you can avoid ;-P )
LG And in case anyone is still reading this now, I'd like to throw out the
LG suggestion that CVS_LOCAL_BRANCH_NUM should really be an option to cvs
LG rtag and should thereby be settable in one's
, $@ is really needed where your parameters
contain spaces (bad practice in filenames, yeah, but don't make yourself
another one PITA you can avoid ;-P )
got it.
LG And in case anyone is still reading this now, I'd like to throw out the
LG suggestion that CVS_LOCAL_BRANCH_NUM should really
I finally figured this out. To use CVS_LOCAL_BRANCH_NUM with a cvs
pserver you need to have the environment variable set server-side. That
means something like invoking a wrapper from inetd which sets the
environment variable and the calls cvs.
Completely undocumented behavior and not terribly
I've been struggling all weekend to setup a local CVS repo mirror, and I
guess I've done that successfully, but I can't figure out what is going on
with CVS_LOCAL_BRANCH_NUM. My understanding is that if I set it to a
large number 63000 that it should tag branches that I make with values
roughly
16 matches
Mail list logo
