Date: Fri, 05 Nov 1999 15:42:39 +0900 From: Yoshinobu Inoue <shin@nd.net.fujitsu.co.jp> To: peter@netplex.com.au Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: CVSROOT avail Message-ID: <19991105154239K.shin@nd.net.fujitsu.co.jp> In-Reply-To: <19991105054331.141241C03@overcee.netplex.com.au> References: <19991105141132W.shin@nd.net.fujitsu.co.jp> <19991105054331.141241C03@overcee.netplex.com.au>
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. 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. Yoshinobu Inoue 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?19991105154239K.shin>