From owner-freebsd-current Sun May 4 12:24:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA12175 for current-outgoing; Sun, 4 May 1997 12:24:13 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA12157 for ; Sun, 4 May 1997 12:24:10 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA14503; Sun, 4 May 1997 12:21:58 -0700 From: Terry Lambert Message-Id: <199705041921.MAA14503@phaeton.artisoft.com> Subject: Re: Help with merging in local changes with CVS etc... To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 4 May 1997 12:21:58 -0700 (MST) Cc: current@FreeBSD.ORG In-Reply-To: <19970504202400.RH45263@uriah.heep.sax.de> from "J Wunsch" at May 4, 97 08:24:00 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > It involves a FreeBSD committer providing a branch tag for local > > use by the committer -- one tag per thread of changes. > > Yep, but this wasn't the problem of the guy asking. Your set of > problems is quite different from his. He wanted to commit changes to his local tree, and have them not stomped on CVSup/CTM update. This is exactly what I want. I don't see why you think our needs are different. The ability to have the commited changes revert the local branching after the commit is a secondary issue, and relies on solving the local commit problem, first. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.