Can you "export" (not check out) the latest files you need from a current vendor branch, which should contain the changes you want (correct), add (not cvs add) your new files, test, and then import all the files to a new vendor branch?
-chris >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] >] On Behalf Of Lemke, Michael IZ/HZA-IOP >Sent: Thursday, July 22, 2004 10:36 AM >To: [EMAIL PROTECTED] >Subject: RE: Import question > > >> From: Christopher.Fouts >> Sent: Thursday, July 22, 2004 4:22 PM >> To: [EMAIL PROTECTED] >> Subject: RE: Import question >> >> >> Test BEFORE importing! > >Sure but I need the merge of the local changes. But I can't >get them without the import or can I? > > >> >> >> >-----Original Message----- >> >From: [EMAIL PROTECTED] >> >[mailto:[EMAIL PROTECTED] >> >] On Behalf Of Larry Jones >> >Sent: Thursday, July 22, 2004 10:12 AM >> >To: Lemke,Michael IZ/HZA-IOP >> >Cc: '[EMAIL PROTECTED]' >> >Subject: Re: Import question >> > >> > >> >Lemke, Michael IZ/HZA-IOP writes: >> >> >> >> When I do a cvs import of a new vendor version the new >> files become >> >> the head revision. I'd like to do the import such that it doesn't >> >> affect HEAD. Only after I've tested the new stuff I want it >> >to become >> >> HEAD. Of course, it should work with local changes merged in just >> >> like the standard way of doing it on the trunk. How can >I do this? >> > >> >Unfortunately, CVS doesn't have any convenient way to let >> you do that. >> > >> >-Larry Jones >> > >> >I told her to expect you to deny everything. -- Calvin >> > >> > > > >_______________________________________________ >Info-cvs mailing list >[EMAIL PROTECTED] >http://lists.gnu.org/mailman/listinfo/info-cvs > _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
