From owner-freebsd-mobile  Wed May 28 06:01:03 1997
Return-Path: <owner-mobile>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id GAA10125
          for mobile-outgoing; Wed, 28 May 1997 06:01:03 -0700 (PDT)
Received: from endo.BBN.COM (ENDO.BBN.COM [128.89.10.99])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id GAA10120
          for <freebsd-mobile@freebsd.org>; Wed, 28 May 1997 06:01:01 -0700 (PDT)
Received: (gdt@localhost) by endo.BBN.COM (8.6.10/8.6.5) id JAA27994; Wed, 28 May 1997 09:00:54 -0400
Date: Wed, 28 May 1997 09:00:54 -0400
Message-Id: <199705281300.JAA27994@endo.BBN.COM>
From: Greg Troxel <gdt@bbn.com>
To: freebsd-mobile@freebsd.org
Subject: hints for CVS with PAO and non-PAO?
Sender: owner-mobile@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I'm involved in a project with Mobile IP and IPSEC, using FreeBSD as
the base.  Normally I'd just import FreeBSD sources from 2.2.2 along
the vendor branch, and hack away locally.  But I'd also like to have
the PAO code in my repository, sort of as a sub-vendor branch.

Since we don't need to stay on the bleeding edge of 2.2, I'm inclined
to import 2.2.x+PAO as the vendor branch.  That is, unpack the pure
2.2.2 sources, apply the appropriate PAO patch, and then import.
Then, any diffs will be relative to 2.2.2+PAO.

I'd be interested in any comments on this scheme, and especially in
any hints about how to do this better.