Bug#535088: Bug number reservation
tag 535088 wontfix
thanks
On Mon, 29 Jun 2009, Joachim Breitner wrote:
> often, I need to know the bug number immediatelly after submitting,
> where waiting for it is annoying.
> For example:
> * I filed a wishlist bug for which I am preparing a patch. I need to
> know the bug number for the Closes: tag in the changelog.
In general, you wouldn't need to know the number for this (unless you
were preparing a NMU diff or something).
> * I filed a bug due to a running discussion, and I would like to reply
> „Good point, I filed a bug, please see http://bugs.debian.org/nnnn
This you can approximate by using X-Debbugs-Cc:, which will include
this information in your response.
[Almost all of the other reasons to know the bug number are part of
#49228, which I'm getting closer and closer to actually fixing.]
> It could be solved by a webpage (and a SOAP-API for transparent
> reportbug support) where you can get a „reserved“ bugnumber (which
> would be one of the next numbers to be assigned, I guess). This
> number then has to be included in the bug submission, via a
> pseudo-header, e.g. Reserved-Bugnumber: 12345
This would require such a massive change to the way we allocate bugs
(and other subtle changes to the codebase which assumes that bug
number equates to filing order) that I can't imagine changing this.
That said, if someone were to go ahead and write such a patch, I could
imagine fixing it. Marking it wontfix just to indicate to myself that
I'm not planning on fixing it, not that I won't consider accepting
such a patch.
Don Armstrong
--
We must realize that today's Establishment is the New George III.
Whether it will continue to adhere to his tactics, we do not know. If
it does, the redress, honored in tradition, is also revolution.
-- William O. Douglas _Points of Rebellion_
http://www.donarmstrong.com http://rzlab.ucr.edu
Reply to: