From owner-freebsd-current  Tue Jul  8 16:29:20 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id QAA16086
          for current-outgoing; Tue, 8 Jul 1997 16:29:20 -0700 (PDT)
Received: from austin.polstra.com (austin.polstra.com [206.213.73.10])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA16076
          for <current@FreeBSD.ORG>; Tue, 8 Jul 1997 16:29:17 -0700 (PDT)
Received: from austin.polstra.com (jdp@localhost)
	by austin.polstra.com (8.8.5/8.8.5) with ESMTP id QAA01070;
	Tue, 8 Jul 1997 16:28:51 -0700 (PDT)
Message-Id: <199707082328.QAA01070@austin.polstra.com>
To: "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com>
cc: current@FreeBSD.ORG
Subject: Re: CVS Branches hits again! 
In-reply-to: Your message of "Tue, 08 Jul 1997 16:11:28 PDT."
             <199707082311.QAA20195@GndRsh.aac.dev.com> 
References: <199707082311.QAA20195@GndRsh.aac.dev.com> 
Date: Tue, 08 Jul 1997 16:28:50 -0700
From: John Polstra <jdp@polstra.com>
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> > Incorrect.  "cvs export" doesn't even accept "-P".  It is implied.
> > Also, as I mentioned, "cvs co -P -D tomorrow src/usr.bin" -- even
> > with the "-P" -- still brings back the pseudo-dead files.
> 
> Then someone should fix the ``usage'' message, or maybe this is
> due to the 2.1-stable nature of the beast I am on right now:

Yes, the usage message is broken on my somewhat-old 2.2-stable
machine.  I notice that it's fixed on my -current machine, though,
and I think it's fixed in up-to-date 2.2-stable as well.

John