From owner-freebsd-lite2 Sun Jul 28 15:15:26 1996 Return-Path: owner-lite2 Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA14299 for lite2-outgoing; Sun, 28 Jul 1996 15:15:26 -0700 (PDT) Received: (from peter@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA14292 for freebsd-lite2; Sun, 28 Jul 1996 15:15:25 -0700 (PDT) Date: Sun, 28 Jul 1996 15:15:25 -0700 (PDT) From: Peter Wemm Message-Id: <199607282215.PAA14292@freefall.freebsd.org> To: freebsd-lite2 Subject: cvs commit: CVSROOT log_accum.pl Sender: owner-lite2@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 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 From owner-freebsd-lite2 Sun Jul 28 15:24:19 1996 Return-Path: owner-lite2 Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA14487 for lite2-outgoing; Sun, 28 Jul 1996 15:24:19 -0700 (PDT) Received: from spinner.DIALix.COM (spinner.DIALix.COM [192.203.228.67]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA14476 for ; Sun, 28 Jul 1996 15:24:11 -0700 (PDT) Received: from spinner.DIALix.COM (localhost.DIALix.oz.au [127.0.0.1]) by spinner.DIALix.COM (8.7.5/8.7.3) with ESMTP id GAA02294 for ; Mon, 29 Jul 1996 06:23:58 +0800 (WST) Message-Id: <199607282223.GAA02294@spinner.DIALix.COM> X-Mailer: exmh version 1.6.6 3/24/96 To: freebsd-lite2@freefall.freebsd.org Subject: Re: cvs commit: CVSROOT log_accum.pl In-reply-to: Your message of "Sun, 28 Jul 1996 15:15:25 MST." <199607282215.PAA14292@freefall.freebsd.org> Date: Mon, 29 Jul 1996 06:23:57 +0800 From: Peter Wemm Sender: owner-lite2@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 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? Cheers, -Peter From owner-freebsd-lite2 Sun Jul 28 23:09:54 1996 Return-Path: owner-lite2 Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA04364 for lite2-outgoing; Sun, 28 Jul 1996 23:09:54 -0700 (PDT) Received: (from hsu@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA04358; Sun, 28 Jul 1996 23:09:52 -0700 (PDT) Date: Sun, 28 Jul 1996 23:09:52 -0700 (PDT) From: Jeffrey Hsu Message-Id: <199607290609.XAA04358@freefall.freebsd.org> To: peter Subject: Re: cvs commit: CVSROOT log_accum.pl Cc: davidg, dyson, freebsd-lite2, phk, terry, wollman Sender: owner-lite2@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > 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? I like the last option, since being able to do a 'cvs update -jbsd_44_lite -jbsd_44_lite_2' is essential and being able to example the logs to resolve conflicts without needing to refer to another tree is highly desirable. Much of my work was done laboriously, by manually examining the cvs diffs of all the previous revisions to see where a line of code was changed. Very late in my effort, the 'cvs annotate' feature was added, which is extremely useful and is a very good reason to have the full logs in the Lite2 tree. From owner-freebsd-lite2 Mon Jul 29 00:17:57 1996 Return-Path: owner-lite2 Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA07291 for lite2-outgoing; Mon, 29 Jul 1996 00:17:57 -0700 (PDT) Received: from relay-4.mail.demon.net (relay-4.mail.demon.net [158.152.1.108]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA07281 for ; Mon, 29 Jul 1996 00:17:54 -0700 (PDT) Received: from post.demon.co.uk ([158.152.1.72]) by relay-4.mail.demon.net id aa11522; 29 Jul 96 7:17 GMT Received: from nlsys.demon.co.uk ([158.152.125.33]) by relay-3.mail.demon.net id aa28581; 29 Jul 96 8:17 +0100 Received: from localhost (dfr@localhost) by nlsys.demon.co.uk (8.7.5/8.6.9) with SMTP id IAA00368; Mon, 29 Jul 1996 08:16:56 +0100 (BST) Date: Mon, 29 Jul 1996 08:16:55 +0100 (BST) From: Doug Rabson Reply-To: Doug Rabson To: Peter Wemm cc: freebsd-lite2@freefall.freebsd.org Subject: Re: cvs commit: CVSROOT log_accum.pl In-Reply-To: <199607282223.GAA02294@spinner.DIALix.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-lite2@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 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 From owner-freebsd-lite2 Mon Jul 29 02:21:02 1996 Return-Path: owner-lite2 Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA15436 for lite2-outgoing; Mon, 29 Jul 1996 02:21:02 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA15428 for ; Mon, 29 Jul 1996 02:20:58 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id LAA00269 for ; Mon, 29 Jul 1996 11:21:14 +0200 (MET DST) To: lite2@freebsd.org Subject: lite2 tactics In-reply-to: Your message of "Sun, 28 Jul 1996 23:12:37 PDT." <199607290612.XAA04445@freefall.freebsd.org> Date: Mon, 29 Jul 1996 11:21:13 +0200 Message-ID: <267.838632073@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-lite2@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Could one of you send a short summary of the current state of the lite2 and what the proposed tactics will be ? In particular I'd like to know if it's OK to pull lite2 fixes over to current still, if this coincides with bugfixing ? -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-lite2 Mon Jul 29 11:01:00 1996 Return-Path: owner-lite2 Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA12808 for lite2-outgoing; Mon, 29 Jul 1996 11:01:00 -0700 (PDT) Received: (from hsu@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA12796; Mon, 29 Jul 1996 11:00:59 -0700 (PDT) Date: Mon, 29 Jul 1996 11:00:59 -0700 (PDT) From: Jeffrey Hsu Message-Id: <199607291800.LAA12796@freefall.freebsd.org> To: dfr@render.com, freebsd-lite2 Subject: Re: cvs commit: CVSROOT log_accum.pl Sender: owner-lite2@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > 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. Two of the sanity checks I use after merging a file are 'cvs diff -rbsd_44_lite' and 'cvs diff -rbsd_44_lite_2' to see eveything that has changed in a file relative to Lite and Lite2. So unless I applied the merge changes to a checked out -current tree, I would not be able to do these checks since a -current imported tree will not have the Lite and Lite2 tags. I also do lots of 'cvs log', 'cvs diff -rrev -rrev+1', and now 'cvs annotate'. With some inconvenience, one could do these on a checked-out -current tree, so the argument to have full history in the lite2 tree is not so strong there. > This way we can use the vendor branch to track the state of -current. Hmm, I think we can still import -current onto the vendor branch even with full history. We certainly need to tag the tree right after the initial import. Peter? From owner-freebsd-lite2 Mon Jul 29 11:12:00 1996 Return-Path: owner-lite2 Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA13562 for lite2-outgoing; Mon, 29 Jul 1996 11:12:00 -0700 (PDT) Received: (from hsu@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA13548 for lite2; Mon, 29 Jul 1996 11:11:58 -0700 (PDT) Date: Mon, 29 Jul 1996 11:11:58 -0700 (PDT) From: Jeffrey Hsu Message-Id: <199607291811.LAA13548@freefall.freebsd.org> To: lite2 Subject: Re: lite2 tactics Sender: owner-lite2@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Could one of you send a short summary of the current state of the > lite2 and what the proposed tactics will be ? Set up initial Lite2 tree from -current. (peter) Bring Lite2 fs patch up to -current and apply to tree. (hsu) Merge in Lite2 NFS. (dfr) Sup. (everyone) Compile, test. (everyone) Read, discuss, review. (everyone) > In particular I'd like to know if it's OK to pull lite2 fixes over to > current still, if this coincides with bugfixing ? That depends on what you have in mind. If it's critical, then of course, else factor in the cost of doing the Lite2 merge later and if it makes sense to bring the fix over now, then go ahead. More concretely, if the fix is isolated and does not conflict with the big Lite patch, then it's okay. From owner-freebsd-lite2 Tue Jul 30 02:18:44 1996 Return-Path: owner-lite2 Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA02102 for lite2-outgoing; Tue, 30 Jul 1996 02:18:44 -0700 (PDT) Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA02097; Tue, 30 Jul 1996 02:18:38 -0700 (PDT) Received: from localhost (dfr@localhost) by minnow.render.com (8.6.12/8.6.9) with SMTP id KAA11237; Tue, 30 Jul 1996 10:20:58 +0100 Date: Tue, 30 Jul 1996 10:20:57 +0100 (BST) From: Doug Rabson To: Jeffrey Hsu cc: freebsd-lite2@freefall.freebsd.org Subject: Re: cvs commit: CVSROOT log_accum.pl In-Reply-To: <199607291800.LAA12796@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-lite2@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 29 Jul 1996, Jeffrey Hsu wrote: > > 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. > > Two of the sanity checks I use after merging a file are 'cvs diff > -rbsd_44_lite' and 'cvs diff -rbsd_44_lite_2' to see eveything that > has changed in a file relative to Lite and Lite2. So unless I > applied the merge changes to a checked out -current tree, I would > not be able to do these checks since a -current imported tree will > not have the Lite and Lite2 tags. > > I also do lots of 'cvs log', 'cvs diff -rrev -rrev+1', and now 'cvs annotate'. > With some inconvenience, one could do these on a checked-out -current > tree, so the argument to have full history in the lite2 tree is > not so strong there. I didn't think of that. In that case, it seems to me that the best thing to do for lite2 is to take a copy of the RCS files for /usr/src/sys and work with that. Hard to merge in stuff from -current though. Hmm. Maybe we should work actually in the current tree but on a development branch in the same way as the TTCP work. > > > This way we can use the vendor branch to track the state of -current. > > Hmm, I think we can still import -current onto the vendor branch > even with full history. We certainly need to tag the tree > right after the initial import. Peter? I thought you could only have one vendor branch. I don't really understand this part of CVS. -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 251 4411 FAX: +44 171 251 0939