* Glenn Morris wrote on Tue, Nov 09, 2010 at 08:34:23AM CET:
Ralf Wildenhues wrote (on Mon, 8 Nov 2010 at 22:46 +0100):
The commands above (Bcc:ed to control at debbugs) should merge and
close both bugs.
The (first) close didn't work, I think it was because your version
number started
Actually, that was probably too glib a response. The version number
information is probably used in other places, and needs to be sortable
so that the fixed/found commands can work. So I don't think arbitrary
version strings can work. You could use the date of a commit perhaps.
* Glenn Morris wrote on Wed, Nov 10, 2010 at 09:46:01PM CET:
Actually, that was probably too glib a response. The version number
information is probably used in other places, and needs to be sortable
so that the fixed/found commands can work. So I don't think arbitrary
version strings can
Ralf Wildenhues wrote (on Mon, 8 Nov 2010 at 22:46 +0100):
BTW, Ouch! I see that my previous reply presenting the patch
has erroneously opended a new, spurious bug report (#7345) in
the tracker! Ralf, could you please you close that report as
invalid?
Not sure how that happened,
merge 7333 7345
tags 7333 + patch
close 7333 v1.11-222-g7a020d6
thanks
* Stefano Lattarini wrote on Sun, Nov 07, 2010 at 03:26:52PM CET:
Now, should I also try to close the bug #7333 on debbugs?
The instruction at http://debbugs.gnu.org/Developer.html seems
quite clear about how to do so, so I
Hello Stefano, Andy,
* Stefano Lattarini wrote on Sat, Nov 06, 2010 at 06:10:44PM CET:
On Friday 05 November 2010, Stefano Lattarini wrote:
I can confirm the bug with latest automake (from git master), with
a much-reduced minimal testcase (see attachment).
I still haven't looked for an
On Friday 05 November 2010, Stefano Lattarini wrote:
I can confirm the bug with latest automake (from git master), with
a much-reduced minimal testcase (see attachment).
I still haven't looked for an explanation or a fix, though.
I've manged to find a very simple fix for the bug (see
