On Wed, 05 Aug 2009, Carl Worth wrote: > [Though, as an off-topic aside here, I do find it confusing as a > user that various pieces of BTS functionality are split among > submit@, control@, and request@ sometimes with different syntax for > the same operation (contrast adding a tag to an original submission > vs. tagging an existing report). I might well propose some > consolidation of the interface to make things easier to use > (obviously keeping all existing interfaces functional).]
control is a superset of request which has operations which modify bugs. submit is for sending mail to a bug. That's really all that there is to it. The main reason that they're separate is historical reasons, and because you have to have some method of disambiguating between "a mail to a bug" and "a message which alters a bug" (or the parts of a message that do that.) See my most recent Debconf talk (when it becomes available, or the slides for it right now) for some more information about why this is the case. Don Armstrong -- Herodotus says, "Very few things happen at the right time, and the rest do not happen at all. The conscientious historian will correct these defects". -- Mark Twain _A Horse's Tail_ http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
