Marc Haber <[EMAIL PROTECTED]> wrote: > On Fri, 8 Dec 2006 12:56:27 -0800, Don Armstrong <[EMAIL PROTECTED]> wrote: >>On Fri, 08 Dec 2006, Marc Haber wrote: >>> On Mon, 4 Dec 2006 16:51:26 -0800, Don Armstrong <[EMAIL PROTECTED]> wrote: >>> >$ GET http://www.debian.org/Bugs/server-control|grep block >>> ><dt><code>block</code> <var>bugnumber</var> <code>by</code> <var>bug</var> >>> >... >>> > <dd>Note that the fix for the first bug is blocked by the other listed >>> > bugs. >>> ><dt><code>unblock</code> <var>bugnumber</var> <code>by</code> >>> ><var>bug</var> ... >>> > <dd>Note that the fix for the first bug is no longer blocked by the other
>>> That's hardly what I'd call "documented". >>What more do you want? That's really all that blocking and unblocking >>does. > What happens to a bug when it's blocked? Which operations do behave as > if the bug were not blocked, which operations behave differently, and > what's the behavioral difference between being blocked and not? Afaik there are no changes in behavior. blocks are only informational. cu andreas -- The 'Galactic Cleaning' policy undertaken by Emperor Zhark is a personal vision of the emperor's, and its inclusion in this work does not constitute tacit approval by the author or the publisher for any such projects, howsoever undertaken. (c) Jasper Ffforde -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]