Date: Mon, 29 Jul 1996 08:16:55 +0100 (BST) From: Doug Rabson <dfr@nlsys.demon.co.uk> To: Peter Wemm <peter@spinner.dialix.com> Cc: freebsd-lite2@freefall.freebsd.org Subject: Re: cvs commit: CVSROOT log_accum.pl Message-ID: <Pine.BSI.3.95.960729081446.290A-100000@nlsys.demon.co.uk> In-Reply-To: <199607282223.GAA02294@spinner.DIALix.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 29 Jul 1996, Peter Wemm wrote: > Peter Wemm wrote: > > peter 96/07/28 15:15:25 > > > > Modified: . log_accum.pl > > Log: > > set lite2 mailing list address > > > > Revision Changes Path > > 1.2 +8 -8 CVSROOT/log_accum.pl > > Well, the list seems to be working, thanks jmb! :-) I took the liberty of > "volunteering" hsu and dfr to be members. > > The CVSROOT is /home/lite2, it can be used remotely with > freefall.freebsd.org:/home/lite2, either in $CVSROOT or with the 'cvs -d > ..' arg. > > I've not yet imported the -current code, because I have some questions > about how everybody will want to use it. In particular, should I just > import -current, or are the 'lite' and 'lite2' tags needed? Or, do you > want a verbatum clone of -current's files as they are right now, with all > the version history which will not be able to be ever updated? > > Unless... cvsup may be able to merge the commits from -current into the > mainline, and you can work on a *branch*. I dont reccomend this though. > > What is needed? I think we only need to have -current imported into the lite2 tree. It is pretty straightforward to use a normal -current cvs tree to examine the lite2 sources and generate diffs. This way we can use the vendor branch to track the state of -current. -- Doug Rabson Mail: dfr@nlsys.demon.co.uk Phone: +44 181 951 1891
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.3.95.960729081446.290A-100000>
