Hi, On Sat, 17 May 2008, Joey Hess wrote: > The state of a bug being a divergence can just be one step in the > life-cycle of a bug. > > Consider a new bug filed one a package, which turns out to be an > upstream bug, is forwarded upstream, gets patched in Debian, and then > has the patch forwarded upstream, so the bug is tagged as a divergence, > and then later upstream fixes it so the bug is closed.
BTW, as a side thought, we could have tools that give list of bugs tagged divergence which are not forwarded and as the task of forwarding those is not really difficult when the patch is well commented, we could have many contributors helping us to forward our patches. (Some corner-case have to be dealt for example when upstream is dead or has no appropriate infrastructure (no ML and no BTS)). This particular case (which I like) goes however in the opposite direction of what I gathered... up to now it looked like that your idea was better suited to be patches.debian.org based on debbugs but not inside bugs.debian.org. Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
