Date: Mon, 24 Mar 1997 22:24:57 -0800 (PST) From: Chris Timmons <skynyrd@opus.cts.cwu.edu> To: Heikki Suonsivu <hsu@clinet.fi> Cc: freebsd-hackers@freebsd.org Subject: Re: cvs usage Message-ID: <Pine.BSF.3.95.970324221559.12314A-100000@opus.cts.cwu.edu> In-Reply-To: <199703250029.CAA14752@news.clinet.fi>
next in thread | previous in thread | raw e-mail | index | archive | help
Here's what I do:
cvs co -P -rRELENG_2_2 src
to start out with (-P is supposedly implied by using -r
but I put it there anyways.)
To update, I've found that you still need to supply the -rRELENG_2_2
because directories (and the files contained within them) that are present
on the main trunk (i.e. current) but not on the RELENG_2_2 branch will be
created if you omit -r. This phenomemon will give you what I call a 2.2+
system which is neither desired nor typically buildable!
For directories that were created on your initial checkout, sticky tags
are present which will cause them to be updated as you expect. So for
example:
cd /usr/src
cvs -q update -Pd -rRELENG_2_2
would be the way to update the tree you created with the initial checkout
shown above. I suppose there are probably 49 reasons why this might be a
goofy way of doing things but it has worked pretty well for me :)
-Chris
On Tue, 25 Mar 1997, Heikki Suonsivu wrote:
>
> Apparently my cvs is rusting or I am just missing something. I have
> checked out RELENG_2_2 from CVS with
>
> check checkout -r RELENG_2_2
>
> and keep updating the checked out copy of the tree with
>
> cvs update
>
> but this apparently fails to update new directories in the CVS tree.
> /bin/chio and couple of files in share/doc/psd like 28.cvs were not
> updated, though Makefile was so make world failed.
>
> What am I doing wrong here ?
>
> --
> Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@clinet.fi
> mobile +358-40-5519679 work +358-9-43542270 fax -4555276
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.970324221559.12314A-100000>