[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bug in autoconf-2.64

From: Ralf Wildenhues
Subject: Re: bug in autoconf-2.64
Date: Sun, 27 Feb 2011 06:52:25 +0100
User-agent: Mutt/1.5.20 (2010-08-04)

* Eric Blake wrote on Sun, Feb 27, 2011 at 12:52:22AM CET:
> > * Ralf Wildenhues wrote on Wed, Feb 23, 2011 at 09:08:07PM CET:
> >> I can confirm the issue, but my bisect ended at
> >> 5e763da323f3927159b6c151f186569a9929ddbe instead.
> Thankfully, 'git describe 5e763da' in m4.git states:
> v1.4.15-3-g5e763da
> That is, no released version of m4 has this commit (only m4 built from
> git).  Unfortunately, you resolved to gnulib commit c823199d, which is
> not related to the bug uncovered this week.

Right.  git bisect only gives you *one* (not necessarily the most or
least recent) commit at which some bug is uncovered on the test system,
not the commit at which it is introduced.  On my system this commit was
the winner because it caused the gnulib strstr replacement to be used.
I don't think I've claimed anything else.  :-)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]