On Thu, 11 Oct 2001, Greg A. Woods wrote: > [ 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. >
It is already done now with 2 vendor branches.. Moving the branch tag to the corresponding vendor version does the job.. I tested commiting of files on the two branches and it all seems to work fine.. Cheers, Gerhard. -- Gerhard Ahuis [EMAIL PROTECTED] Unsolicited advertisements subject to $1000 consulting fee. _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs