From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/71782 Path: news.gmane.org!not-for-mail From: Russ Allbery Newsgroups: gmane.emacs.gnus.general Subject: Re: Any juicy outstanding Gnus bugs? Date: Sat, 25 Sep 2010 15:53:11 -0700 Organization: The Eyrie Message-ID: <87r5ghbfl4.fsf@windlord.stanford.edu> References: <87r5ghwpnr.fsf@keller.adm.naquadah.org> <87lj6pwo9n.fsf@keller.adm.naquadah.org> <87zkv5y2g4.fsf@turtle.gmx.de> <878w2p7azn.fsf@mid.gehheimdienst.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1285455254 27223 80.91.229.12 (25 Sep 2010 22:54:14 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sat, 25 Sep 2010 22:54:14 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M20155@lists.math.uh.edu Sun Sep 26 00:54:12 2010 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1OzddC-0005M2-En for ding-account@gmane.org; Sun, 26 Sep 2010 00:54:10 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1Ozdcs-0001LF-9a; Sat, 25 Sep 2010 17:53:50 -0500 Original-Received: from mx1.math.uh.edu ([129.7.128.32]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1Ozdcq-0001L0-L8 for ding@lists.math.uh.edu; Sat, 25 Sep 2010 17:53:48 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx1.math.uh.edu with esmtp (Exim 4.72) (envelope-from ) id 1Ozdcm-0005sV-EE for ding@lists.math.uh.edu; Sat, 25 Sep 2010 17:53:48 -0500 Original-Received: from smtp4.stanford.edu ([171.67.219.84] helo=smtp.stanford.edu) by quimby.gnus.org with esmtp (Exim 3.36 #1 (Debian)) id 1Ozdcl-00035T-00 for ; Sun, 26 Sep 2010 00:53:43 +0200 Original-Received: from smtp.stanford.edu (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id D3466CA5D for ; Sat, 25 Sep 2010 15:53:11 -0700 (PDT) Original-Received: from windlord.stanford.edu (windlord.Stanford.EDU [171.67.225.134]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.stanford.edu (Postfix) with ESMTPS id 4809BCA36 for ; Sat, 25 Sep 2010 15:53:11 -0700 (PDT) Original-Received: by windlord.stanford.edu (Postfix, from userid 1000) id 2F6E42F48E; Sat, 25 Sep 2010 15:53:11 -0700 (PDT) In-Reply-To: (Lars Magne Ingebrigtsen's message of "Sun, 26 Sep 2010 00:12:03 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) X-Spam-Score: -4.9 (----) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:71782 Archived-At: Lars Magne Ingebrigtsen writes: > Frank Schmitt writes: >> The interface is rather fiddly. It works by sending mails including >> commands to the e-mail address specific for this bug. See >> http://debbugs.gnu.org/server-control.html > Hm. Kinda awkward if you're doing drive-by stuff... It's the same system we use for Debian, and for Debian there's a script (bts) in the devscripts package that completely automates sending mail. So I'd just type things like: bts tag 435 confirmed , tag 437 wontfix , close 478 at the command line and all the right things happen. I don't know how difficult it would be to repoint bts at the Emacs bug tracker. It shouldn't be particularly hard. People in Debian are strongly encouraged to close bugs only by copying NNNN-close@bugs.debian.org in the e-mail message explaining why you're closing the bug. That best practice ensures that people get an explanation rather than the bug just being quietly closed. I don't know if Emacs has a similar policy. The idea of the BTS design is to let you do nearly everything in e-mail as part of replying to the user's bug, without needing to interact with some other interface very much. You can, for instance, just add the bug commands to the start of an e-mail reply and bcc the control address. -- Russ Allbery (rra@stanford.edu)