Re: Keeping using locally modified source

2000-03-06 Thread Sheldon Hearn
On Thu, 02 Mar 2000 19:59:39 EST, James Howard wrote: > The problem is how do we keep up with -STABLE afterwards? Using > CVSup, out changes will get clobbered every time. Is there a facility > where you can keep up with the source but let local modifications > through? CVS does this beautif

Re: Keeping using locally modified source

2000-03-05 Thread John Polstra
In article <[EMAIL PROTECTED]>, Bill Fenner <[EMAIL PROTECTED]> wrote: > > I've got this program in my head that takes a CVS tree and turns it > into a branch ofanother CVS tree (e.g. FreeBSD rev 1.7 turns into > rev 1.1.1.7) but it's never managed to make it out of my head, so > it must be hard

Re: Keeping using locally modified source

2000-03-04 Thread Bill Fenner
I've got this program in my head that takes a CVS tree and turns it into a branch ofanother CVS tree (e.g. FreeBSD rev 1.7 turns into rev 1.1.1.7) but it's never managed to make it out of my head, so it must be harder than I keep thinking it is =) Bill To Unsubscribe: send mail to [EMAIL PRO

Re: Keeping using locally modified source

2000-03-03 Thread Assar Westerlund
Don Lewis <[EMAIL PROTECTED]> writes: > I thought about using this, but it doesn't appear to be easy to track > changes to an official branch. I was looking for something that would > be as easy tracking changes made by infrequent imports on the vendor > branch. No, it's just a hack. Having hie

Re: Keeping using locally modified source

2000-03-03 Thread Don Lewis
On Mar 3, 11:47am, Assar Westerlund wrote: } Subject: Re: Keeping using locally modified source } There's even a hack in FreeBSD cvs and cvsup to allow you to keep a } `local' branch that's not clobbered by cvsup, namely the environment } variable CVS_LOCAL_BRANCH_NUM. I thou

Re: Keeping using locally modified source

2000-03-03 Thread Assar Westerlund
Brooks Davis <[EMAIL PROTECTED]> writes: > Yup, just use cvsup to maintain an up to date copy of the repository > localy and then cvs checkout your source tree from there. This allows > you to keep in sync and keep local modifications in your tree. Updates > take longer and I recommend updating

RE: Keeping using locally modified source

2000-03-03 Thread Koster, K.J.
> > > The problem is how do we keep up with -STABLE > > afterwards? Using CVSup, out changes will get clobbered > every time. Is > > there a facility where you can keep up with the source but let local > > modifications through? > > Yup, just use cvsup to maintain an up to date copy of the rep

Re: Keeping using locally modified source

2000-03-02 Thread Brooks Davis
On Thu, Mar 02, 2000 at 07:59:39PM -0500, James Howard wrote: > At a site I am working at, we need to be able to limit which users can > bind a socket to an address under IPv4. Basically, bind() needs to check > the caller's groups and if you are one of several allowable groups, let it > pass, ot

Keeping using locally modified source

2000-03-02 Thread James Howard
At a site I am working at, we need to be able to limit which users can bind a socket to an address under IPv4. Basically, bind() needs to check the caller's groups and if you are one of several allowable groups, let it pass, otherwise, error out. Now, I glanced over the bind() code and it does n