Reopening bugs closed without explanation

[Jeroen van Wolffelaar]

Hi Arnaud!

On Fri, May 13, 2005 at 09:21:15AM +0200, Arnaud Vandyck wrote:
> Thu, 12 May 2005 23:57:51 +0200, 
> Jeroen van Wolffelaar <jeroen@wolffelaar.nl> wrote: 
> > My only point was that when you did look into what bugs can be closed,
> > it shouldn't be too much effort to also briefly describe that in the
> > closing message for the benefit of the submitter.
> 
> I was very busy and closed those bugs because they were no more
> relevant. I should use the control@bugs.debian.org addresss and not the
> #-done@b.d.o, then I could put the same message for every bug.

That still won't give any meaningful message to the bug submitters at
all. What works best in this situation is what Wolfgang did:

| To: 176763-done@bugs.debian.org
| CC: 188460-done@bugs.debian.org,  151007-done@bugs.debian.org, 
|  141334-done@bugs.debian.org,  154155-done@bugs.debian.org
| Subject: lib-saxon-java removed and replaced by libsaxon-java
| 
| as the subject says lib-saxon-java is removed from
| testing/unstable and replaced with libsaxon-java.
| 
| Therefore the following bugs reassigned to
| libsaxon-java are already done:
|
| (and why that is for each bug)

This is simply one mail to rule them all :)
 
Kind regards, and I hope you'll find these bug system tricks useful!

--Jeroen

-- 
Jeroen van Wolffelaar
Jeroen@wolffelaar.nl (also for Jabber & MSN; ICQ: 33944357)
http://Jeroen.A-Eskwadraat.nl