From owner-freebsd-hackers Wed Sep 5 13:36: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id DE91F37B407 for ; Wed, 5 Sep 2001 13:35:53 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f85KZnX25193; Wed, 5 Sep 2001 14:35:49 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f85KZnh47772; Wed, 5 Sep 2001 14:35:49 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200109052035.f85KZnh47772@harmony.village.org> To: Julian Elischer Subject: Re: local changes to CVS tree Cc: John Polstra , hackers@FreeBSD.ORG, nate@yogotech.com In-reply-to: Your message of "Wed, 05 Sep 2001 13:41:19 PDT." References: Date: Wed, 05 Sep 2001 14:35:49 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message Julian Elischer writes: : As a workaround, people could just gat the source each week : and do an cvs import into the vendor branch via script.. : (of course with doing it correctly you could have matching version numbers : on the vendor branch) As someone who does lots of vendor branch imports of FreeBSD into cvs, I can tell you that automating it is fraught with dangers if you have any significant changes in your base tree. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message