Date: Fri, 9 Jan 1998 16:08:57 -0800 (PST)
From: Dean Gaudet <dgaudet@arctic.org>
To: new-httpd@apache.org
Subject: Re: Intel Port & Release Process
In-Reply-To: <Pine.BSF.3.95q.980109105954.23397A-100000@valis.worldgate.com>
Message-ID: <Pine.LNX.3.95dg3.980109160819.21012G-100000@twinlark.arctic.org>
Organization: Transmeta Corp.
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: new-httpd-owner@apache.org
Precedence: bulk
Reply-To: new-httpd@apache.org


On Fri, 9 Jan 1998, Marc Slemko wrote:

> On Fri, 9 Jan 1998, Jim Jagielski wrote:
> 
> > Ben Laurie wrote:
> > > 
> > > Marc Slemko wrote:
> > > > The problem is that much of the code here is more interrelated and needs
> > > > to be better on a per line basis because it simply isn't as big as some
> > > > projects.  Voting has raised a heck of a lot of objections to all sorts of
> > > > patches, mine included.  You can do this stuff after the fact, but the
> > > > problem is that if no one has time to pursue it, it just falls away.
> > > 
> > > I'd say that the solution to this is to say that if anyone has a problem
> > > with a particular patch then it MUST be backed out and use the
> > > review-then-commit model.
> > > 
> > 
> > >From a totally clueless person (and it might be in the FMs) how does
> > one back out a specific commit?
> 
> You don't.  CVS doesn't support it.

cvs update -D yesterday

> You just find the diff, reverse (eg. diff the version nums in the opposite
> directory, patch -R, etc) it and apply it. 

This usually works quite well with the stuff mailed to apache-cvs.  I've
used it to back out patches, and to apply patches between trees.

Dean