unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: emacs-devel@gnu.org
Subject: Re: debbugs.el revisited
Date: Thu, 30 Jun 2011 23:08:51 +0200	[thread overview]
Message-ID: <m3vcvnkows.fsf@quimbies.gnus.org> (raw)
In-Reply-To: 87iprn6nic.fsf@stupidchicken.com

Chong Yidong <cyd@stupidchicken.com> writes:

>> debbugs.el currently lives in GNU ELPA.  Can I check it into the Emacs
>> sources for easier continued development and usage?
>
> Please work in the GNU ELPA repository.

I think the debbugs.el interface is very usable now, and should be used
by both developers and users to check and track bug reports.  It's
certainly more convenient than the web interface.

So I think it should go into Emacs.  But you're the boss.

> According to the Debbugs SOAP interface documentation at
>
> http://wiki.debian.org/DebbugsSoapInterface
>
> the get_status method accepts multiple bug numbers, so it should only be
> necessary to make one request.

Yeah, I found that out after a while.

Is there any particular reason emails sometimes take hours to get posted
to the mailing list?  It's kinda odd...

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/




  reply	other threads:[~2011-06-30 21:08 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-30 17:57 debbugs.el revisited Lars Magne Ingebrigtsen
2011-06-30 19:49 ` Lars Magne Ingebrigtsen
2011-06-30 20:45 ` Michael Albinus
2011-06-30 21:02 ` Chong Yidong
2011-06-30 21:08   ` Lars Magne Ingebrigtsen [this message]
2011-06-30 23:26     ` Glenn Morris
2011-06-30 23:34       ` Lars Magne Ingebrigtsen
2011-07-01  2:28     ` Stefan Monnier
2011-07-01  7:12       ` Eli Zaretskii
2011-07-01  8:59         ` Štěpán Němec
2011-07-01  9:25     ` Julien Danjou
2011-07-01 11:16       ` Michael Albinus
2011-07-02  1:14         ` Glenn Morris
2011-07-02 12:58           ` Lars Magne Ingebrigtsen
2011-07-02 13:04             ` Michael Albinus
2011-07-02 17:48             ` Glenn Morris
2011-07-02 18:03               ` Michael Albinus
2011-07-02 18:08                 ` Glenn Morris
2011-07-02 20:14               ` Lars Magne Ingebrigtsen
2011-07-02 20:54                 ` Lars Magne Ingebrigtsen
2011-07-02 21:09                   ` Christoph Scholtes
2011-07-02 21:15                     ` Lars Magne Ingebrigtsen
2011-07-02 22:19                       ` Lars Magne Ingebrigtsen
2011-07-02 23:08                       ` joakim
2011-07-04 14:47                         ` Stefan Monnier
2011-07-03  0:09                       ` Christoph Scholtes
2011-07-03  6:34                         ` Michael Albinus
2011-07-02 22:30                   ` Glenn Morris
2011-07-03  4:48               ` Jason Rumney
2011-07-03 11:07                 ` Andreas Schwab
2011-07-02 16:37           ` Michael Albinus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3vcvnkows.fsf@quimbies.gnus.org \
    --to=larsi@gnus.org \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).