help-debbugs
[Top][All Lists]
Advanced

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

Re: bug#7333: [PATCH] {maint} Fix a bug in variable concatanation with `


From: Ralf Wildenhues
Subject: Re: bug#7333: [PATCH] {maint} Fix a bug in variable concatanation with `+='.
Date: Tue, 9 Nov 2010 20:11:19 +0100
User-agent: Mutt/1.5.20 (2010-08-04)

Hello help-debbugs!

* Stefano Lattarini wrote on Tue, Nov 09, 2010 at 12:05:30PM CET:
> On Tuesday 09 November 2010, Ralf Wildenhues wrote:
> > * Stefano Lattarini wrote on Mon, Nov 08, 2010 at 11:35:26PM CET:
> > > > The commands above (Bcc:ed to control at debbugs) should merge and
> > > > close both bugs.
> > > Thanks for doing that.  But I think it would have been better to merge
> > > #7345 in #7333.
> > 
> > Huh?  That is exactly what I did.
> Then why it is "#7345" and not "#7333" which appeared in the list of
> "Outstanding bugs" (and appears ow in the list of "Resolved bugs")?
> Or is it debbugs which, when two bug reports are merged, automatically
> keeps the most recent one of them visible?

On http://debbugs.gnu.org/server-control.html it is documented that with
  forcemerge N1 N2

N1 will become the master bug.  Apparently that is not the same with
  merge N1 N2

No; wait.

When I look at http://debbugs.gnu.org/cgi/pkgreport.cgi?pkg=automake
then it shows 7333 not 7345.
When I look at
http://debbugs.gnu.org/cgi/pkgreport.cgi?package=automake;max-bugs=100;base-order=1;bug-rev=1
then it shows 7345 not 7333.  The latter is linked from the main debbugs
page, the former is redirected from http://debbugs.gnu.org/automake

It seems the bug-rev=1 is the cause here.  This looks like a debbugs bug
to me.  Where should I report it?

Thanks,
Ralf



reply via email to

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