[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CVS export

From: Stewart Brodie
Subject: Re: CVS export
Date: Fri, 19 Oct 2001 10:56:35 +0100
User-agent: Messenger-Pro/2.58beta3 (Newsbase/0.61b) (RISC-OS/4.00-Ursula002f) NewsHound/1.43-pre1

In message <address@hidden>
          address@hidden (John Minnihan) wrote:

> In all the years I've used CVS, I've institutionalized use of 'cvs 
> export' only briefly at one client.  And that was only to  satisfy some 
> nimrod (who didn't understand cvs) who screamed - repeatedly - "get rid 
> of all these CVS files!".  Presence - or absence - of the CVS admin 
> structure hasn't had the slightest impact (positively or negatively on 
> its own merit)on the success of failure of any of the thousands of 
> releases I've produced.  Period.  'cvs co' with a known tag is the way 
> to go.

I agree that I prefer 'cvs co'.  We run automated builds of several products
and prefer to have incremental updates to the source tree (thus requiring
checkout not export).

Plus I seem to recall that in CVS 1.10.8, you cannot export directories that
have default log messages specified in rcsinfo (you get an error about not
being able to create CVS/Entries files). We would use 1.11.1p1, but we've had
to revert to 1.10.8 as CVS 1.11.1p1 dies with protocol errors all over the
place during the nightly checkouts.

>From an exporting point of view, the issue of not knowing what sources
comprised any particular build is a non-issue for us - each product is
defined in terms of a text file (held in CVS) containing a list of
directories and symbolic tags.  In that case, a product can be defined in its
entirety by the revision or date of this single file (which contains $Id$ in
a comment at the top to identify it)

Stewart Brodie, Senior Software Engineer
Pace Micro Technology PLC
645 Newmarket Road
Cambridge, CB5 8PB, United Kingdom         WWW:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]