[Top][All Lists]

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

RE: Lying about the author (and so).

From: EXT-Corcoran, David
Subject: RE: Lying about the author (and so).
Date: Wed, 17 Apr 2002 09:22:19 -0700

> -----Original Message-----
> From: address@hidden [mailto:address@hidden
> Sent: Sunday, April 14, 2002 11:10 AM
> To: CVS-II Discussion Mailing List
> Subject: Re: Lying about the author (and so).
> [ On Sunday, April 14, 2002 at 03:21:26 (-0400), gabriel 
> rosenkoetter wrote: ]
> > Subject: Re: Lying about the author (and so).
> >
> Why would a bunch of programmers writing new code want to use '-ko'?
> You should _NOT_ use 'cvs import' _unless_ you're managing third-party
> code.

This conflicts with another opinion I found on usenet (link below):

        I think almost EVERYONE gets bit by this at first.  The CVS
        mantra is "import, delete, checkout".  You need to import
        your sources then check them out to a different location
        before you can really get to work with CVS.  That's the easy

He also suggests an alternate:

        Another way to do it is to create the top level dir that will
        hold your sources inside the CVS repository, check out that
        "empty" project, copy your source tree to your checked out
        dir and then add everything from there.  I've done it both
        ways and import is MUCH easier.

So what is the prefered method of creating a new project given you are *NOT*
third party code?



"Only the rare taxpayer would be likely to know that he could refuse to
produce his records to IRS agents ... Who would believe the ironic truth
that the cooperative taxpayer fares much worse than the individual who
relies upon his constitutional rights." -- U.S. Federal Judge Cummings, in
U.S. v. Dickerson (7th Circuit 1969)

reply via email to

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