Your message dated Wed, 23 May 2012 13:10:41 -0500
with message-id <20120523181041.GB18286@burratino>
and subject line Re: bugs.debian.org: missing messages on
http://bugs.debian.org/640823
has caused the Debian Bug report #649475,
regarding bugs.debian.org: bug closure doesn't show up in history of merged bugs
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
649475: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649475
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bugs.debian.org
Severity: normal
Bug 640823 was closed on 9 Nov 2011 (after the last merge), but on
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640823
the messages stop on 20 Oct 2011 (so that one doesn't see the close
message on this page; one needs to search the merged bugs).
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Don Armstrong wrote:
> On Wed, 23 May 2012, Jonathan Nieder wrote:
>> 2011-09-07 merged with #640467
>> 2011-10-02 forcibly merged with #644026
>> 2011-10-20 forcibly merged with #645963
>> 2011-11-09 #640467 closed
>>
>> I'm inclined to agree that the bug closure should show up as a line
>> item on the other merged bugs. Don, any advice in case someone wants
>> to work on that?
>
> It should actually show up now in bugs which have been merged after
> April, 2012. For bugs earlier than that, it's not really worth it.
Thanks. Closing, though I'd be happy to reopen this if someone wants
to figure out a way to deal with the older bugs or document this
gotcha somewhere.
--- End Message ---
