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 <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?