[ On Monday, October 1, 2001 at 09:12:24 (+0000), Gerhard Ahuis wrote: ]
> Subject: Re: Howto solve this in cvs ?
>
> Greg A. Woods <[EMAIL PROTECTED]> wrote:
> >
> > For many of the same reasons it's literally impossible to ever have true
> > multi-vendor support too -- all the benefits of "cvs import" are
> > completely impossible to achieve with multiple vendor branches. You can
> > do multi-vendor tracking manually, but it's one hell of a lot more work
> > (more work even than managing several variant branches in a locally
> > initiated project)!
>
> There are not many files, so if you can give me some hints to let a second
> vendor branch showup on a normal cvs branch and not on the main, I will be
> very thankfull.
Well, it's really quite straight forward. You simply have to create
normal branches for each vendor, and corresponding working directories
for each, and then manually commit and tag each new release on each
release.
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
