From owner-freebsd-hackers  Wed Dec 11 23:16:58 1996
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id XAA25467
          for hackers-outgoing; Wed, 11 Dec 1996 23:16:58 -0800 (PST)
Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA25462
          for <hackers@freebsd.org>; Wed, 11 Dec 1996 23:16:55 -0800 (PST)
Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.3/CET-v2.1) with SMTP id HAA07265; Thu, 12 Dec 1996 07:16:43 GMT
Date: Thu, 12 Dec 1996 16:16:43 +0900 (JST)
From: Michael Hancock <michaelh@cet.co.jp>
To: Marc Slemko <marcs@znep.com>
cc: hackers@freebsd.org
Subject: Re: CVS branch update oddity
In-Reply-To: <Pine.BSF.3.95.961211225134.29879I-100000@alive.ampr.ab.ca>
Message-ID: <Pine.SV4.3.95.961212161345.7215A-100000@parkplace.cet.co.jp>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Wed, 11 Dec 1996, Marc Slemko wrote:

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

I had a similar problem.  My .cvsrc file had a update -A in it that caused
it to ignore sticky tags.

If you want to be sure put the following into your .cvsrc file:

update -P -rRELENG_2_1_0
 
Regards,


Mike