Date: Fri, 5 Nov 1999 00:24:48 -0800 (PST) From: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net> To: shin@nd.net.fujitsu.co.jp (Yoshinobu Inoue) Cc: peter@netplex.com.au, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: CVSROOT avail Message-ID: <199911050824.AAA52874@gndrsh.dnsmgr.net> In-Reply-To: <19991105154239K.shin@nd.net.fujitsu.co.jp> from Yoshinobu Inoue at "Nov 5, 1999 03:42:39 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> > For KAME-supplied files, then yes, an import is exactly the right thing to > > do and it enables simple tracking of KAME releases. However, for files > > that KAME has had to patch, 'cvs import' is not the tool to use. The > > netinet6 and altq etc files are now present in -current as a result of the > > import. > > But current KAME SNAP is based on FreeBSD3.3 so now I think my > approach was essentialy wrong. > I should have created KAME branch to RELENG_3_3_0_RELEASE, and > commit KAME diffs on that branch, and just refer the diffs on > that branch for work on HEAD branch. New code is not allowed to enter the tree via branch -stable, see my other email on my offer to help get the code in a more correct form for import/commit. > However now I feel like just creating local diffs for my own > reference is safer. > If possible, I wish all files and patches I imported last > tiime will disappear from repository. I am sure Peter is working on this, and that the end results will be as if the 2 import attempts never happened. I also further suspect that your commit op's may be suspended for a bit, but perhaps not. I would also wish that perhaps you read the cvs committers guide at this time. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199911050824.AAA52874>