Re: cvs import help

Thanks eveyone.

On Wed, Oct 15, 2008 at 2:16 PM, <[email protected]> wrote:

> That's good info, Larry.  Thanks.
>
> Can we get this into the FAQ?
>
> The issue that I ran into recently while automating the interaction with
> a repository was that files' originally being added to the vendor branch
> messed me up for branching and merging back to the TRUNK.  I had to go
> through some gyrations to set it up so that, when I imported the
> repository the first time, all my files found their way back to the
> root.
>
> What's nice about having versions that look like 1.x is that it's very
> easy then to check to see if the revision is on the TRUNK or not.
>
> In any case this was very helpful.  Thanks again.
>
> Eric
>
>
> > -----Original Message-----
> > Sent: Wednesday, October 15, 2008 4:40 PM
> > To: [email protected]
> > Cc: [email protected]
> > Subject: Re: cvs import help
> >
> > [email protected] writes:
> > >
> > > Why I am getting branchs here? how can I avoid this?
> >
> > In CVS 1.11, import always creates a (vendor) branch.  It's
> > no big deal and you shouldn't worry about it.  However, you can avoid
> it by using
> > CVS 1.12 (where import has an option to not create a branch) or by not
> > using import.  You usually add a directory to an existing project by
> > adding the directory in a checked-out working directory and
> > doing ``cvs add'' rather than using import.  (You can also use the
> same method to
> > add a whole new project by checking out the top-level of the
> > repository without recursion [so you don't get all the files] using
> the slightly
> > magic module name ``.''.)
> >
> > > What I want is something like this.
> > > I don't need 1.1.1.1!!!!
> > > I need versions to be 1.1 1.2 1.3.
> >
> > Version numbers are for CVS internal use only -- you
> > shouldn't care what they are.
> > --
> > Larry Jones
> >
> _______________________________________________
>
> This e-mail may contain information that is confidential, privileged or
> otherwise protected from disclosure. If you are not an intended recipient of
> this e-mail, do not duplicate or redistribute it by any means. Please delete
> it and any attachments and notify the sender that you have received it in
> error. Unless specifically indicated, this e-mail is not an offer to buy or
> sell or a solicitation to buy or sell any securities, investment products or
> other financial product or service, an official confirmation of any
> transaction, or an official statement of Barclays. Any views or opinions
> presented are solely those of the author and do not necessarily represent
> those of Barclays. This e-mail is subject to terms available at the
> following link: www.barcap.com/emaildisclaimer. By messaging with Barclays
> you consent to the foregoing.  Barclays Capital is the investment banking
> division of Barclays Bank PLC, a company registered in England (number
> 1026167) with its registered office at 1 Churchill Place, London, E14 5HP.
>  This email may relate to or be sent from other members of the Barclays
> Group.
> _______________________________________________
>