From owner-freebsd-hackers  Wed Dec 11 22:31:38 1996
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id WAA22969
          for hackers-outgoing; Wed, 11 Dec 1996 22:31:38 -0800 (PST)
Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA22964
          for <hackers@freebsd.org>; Wed, 11 Dec 1996 22:31:33 -0800 (PST)
Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.7.5/8.7.3) with UUCP id XAA20591 for hackers@freebsd.org; Wed, 11 Dec 1996 23:31:32 -0700 (MST)
Received: from localhost (marcs@localhost) by alive.ampr.ab.ca (8.7.5/8.7.3) with SMTP id XAA03818 for <hackers@freebsd.org>; Wed, 11 Dec 1996 23:31:08 -0700 (MST)
Date: Wed, 11 Dec 1996 23:31:08 -0700 (MST)
From: Marc Slemko <marcs@znep.com>
X-Sender: marcs@alive.ampr.ab.ca
To: hackers@freebsd.org
Subject: CVS branch update oddity
Message-ID: <Pine.BSF.3.95.961211225134.29879I-100000@alive.ampr.ab.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Ok, so I do a
	cvs checkout -rRELENG_2_1_0 src

Why can't I use a
	cvs update -dP src

to keep it up to date?  If I try, it will bring in newly created
directories in other branches.  If I use
	cvs update -dP -rRELENG_2_1_0 src

it seems to work as expected but, in general, the -r flag to checkout is
supposed to be sticky.  The man page seems to imply that I should not need
to specify the -r for the update. 

This is using cvs 1.6.3pl2, which is what is in -stable.  It may
well just be a bogon in the old version, but didn't notice a mention
of the problem being fixed in the ChangeLog for the current version...