[cvsnt] Re: vendor branch and import problem

Oliver Giesen ogware at gmx.net
Thu Feb 26 16:38:52 GMT 2004

Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.

Tony Hoyle wrote:

> They don't really work like that.  That would require baseline support
> which I'm not aware any of 'free' systems support. 

What exactly do you mean by that? I am apparently still ignorant to your 
statement that Import never worked in the first place as this is totally 
contrary to my experience...

 > An import will
> allow you to update your sources

It no longer does... :(

 > but you end up putting all your
> changes back in, which is a pain (I avoid import and do it manually,
> myself).

Yes, it's a matter of merging back and forth. Hasn't been much of an 
effort so far. However, my case is probably a bit special in this 
respect as the local modifications I make eventually get contributed to 
the "official" third-party sources anyway. All I usually have to do when 
we get the next third-party release is use cvs admin -b to reset the 
default branch to the vendor branch...


In everybody's best interest, please do not post or CC technical
questions to me in private unless they are specifically about a
macro/product of mine that is NOT already bundled with WinCvs. I will
generally forward my replies to such posts to the CVSGUI list without
further notice.
----	------------------
JID:	ogiesen at jabber.org
ICQ:	18777742	(http://wwp.icq.com/18777742)

More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook