GNU bug report logs -
#4922
<control>
Previous Next
Reported by: Per Starbäck <per.starback <at> gmail.com>
Date: Fri, 13 Nov 2009 21:05:06 UTC
Severity: minor
Tags: confirmed
Done: Eli Zaretskii <eliz <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
Message #34 received at 4922 <at> debbugs.gnu.org (full text, mbox):
> >> > And AFAICT it does seem to be fixed. Should it be closed?
> >> >
> >> > http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16216
> >>
> >> That 16216 is a duplicate of this bug, isn't it? Since it is fixed the
> >> original is also fixed.
> >
> > Yes, except it is the other way around. AFAICT, that bug (and
> > so this one) has already been fixed.
> >
> > But perhaps Fuqiao is seeing something different and there is
> > still a bug somewhere.
>
> As the original reporter from 2011 I maintain that that is the
> original, and not the one from last December. What I meant with "since
> it is fixed the original is also fixed" was that it was the copy that
> finally triggered the fix.
I see what you are saying. AFAICT:
1. Yes, 16216 is a duplicate of 4922 (I had it backward; sorry).
2. Yes, it was the duplicate, 16216 that triggered fixing (by Eli).
3. Yes, it seems to be fixed.
4. But we should perhaps wait to hear from Fuqiao wrt whether
he can repro it with the latest code.
If he can confirm that this is fixed, 4922 and 16216 can be
closed (no?).
This bug report was last modified 11 years and 145 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.