[Top][All Lists]

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

Re: Vendor Branches

From: Greg A. Woods
Subject: Re: Vendor Branches
Date: Sat, 4 Jan 2003 18:24:33 -0500 (EST)

[ On Saturday, January 4, 2003 at 20:05:46 (-0000), John Birtley wrote: ]
> Subject: Vendor Branches
> The problem is that I want to be able to copy the latest version on the
> vendor branch to the latest version on the INTEGRATION branch, since all
> integration testing and tagging is to be done from this branch, i.e.:

You cannot safely mix normal branches in modules with vendor branches
and still expect full and normal functionality from CVS.

To do what you want you'll have to manually "import" (i.e. copy and add)
new vendor releases to a normal branch and then manually merge to the
other branches you wish to maintain..


> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

Please DO NOT EVER send HTML, rich text, or otherwise stylized e-mail,
especially not to me or to any public mailing list.  Not all mail
readers will recognize such formats, and their added volume is generally
a total waste of bandwidth, storage, and processing power for everyone.
HTML in particular is a potential security threat and many firewalls and
some mailing lists filter it entirely -- especially since CERT and
Microsoft have jointly anounced a very major flaw in the HTML rendering
engine used in all Microsoft products (in versions still widely in use,
and which isn't even properly fixed in the most recent releases).

For more information see, for instance, the following article:

Please send all your messages as plain text only.

                                                                Greg A. Woods

+1 416 218-0098;            <address@hidden>;           <address@hidden>
Planix, Inc. <address@hidden>; VE3TCP; Secrets of the Weird <address@hidden>

reply via email to

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