[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] Fix potential regressions in depcomp{3,5}.test.
From: |
Ralf Wildenhues |
Subject: |
Re: [PATCH] Fix potential regressions in depcomp{3,5}.test. |
Date: |
Wed, 18 Aug 2010 20:40:24 +0200 |
User-agent: |
Mutt/1.5.20 (2010-04-22) |
* Stefano Lattarini wrote on Wed, Aug 18, 2010 at 08:35:20PM CEST:
> On Wednesday 18 August 2010, Ralf Wildenhues wrote:
> > Ideally, you'd commit this to a temporary branch based off of the
> > patch that introduced the regression, and merge that branch into
> > maint. If we follow this strategy consistently, then there one can
> > simply merge the temp branch into all branches that have the
> > parent.
> Smart. Would make another nice addition for HACKING ;-)
Already in HACKING, well, sort-of:
* For bug fixes of long-standing bugs, it may be useful to commit them to
a new branch based off of the commit that introduced the bug, and merge
this bugfix branch into active branches that descend from the buggy commit.
> BTW, how should I call that temporary branch?
Dunno; whatever you like. fix-depcomp-tests? I name them fix-* in some
projects. It doesn't really matter for anything but the merge log entry.
Cheers,
Ralf