Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: emacs-devel@gnu.org
Cc: ding@gnus.org
Subject: Re: debbugs.el
Date: Fri, 25 Feb 2011 09:59:05 +0000	[thread overview]
Message-ID: <87hbbsxwnq.fsf@gnus.org> (raw)
In-Reply-To: <8339ncsf3e.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

> Or make the bugs come to you: subscribe to the bug-gnu-emacs@gnu.org
> mailing list, and that's it.

I do read that list.  The purpose of a debbugs interface is to read (and
check) the status of older bugs.

Or are you saying that there's no value in being able to view the status
of the debbugs archive?

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen




      parent reply	other threads:[~2011-02-25  9:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8762sa9770.fsf@gmx.de>
     [not found] ` <87pqqibr30.fsf@stupidchicken.com>
     [not found]   ` <87mxllambw.fsf@marauder.physik.uni-ulm.de>
2011-02-24 11:33     ` debbugs.el Michael Albinus
2011-02-24 23:44       ` debbugs.el Evgeny M. Zubok
2011-02-25 10:55         ` debbugs.el Michael Albinus
2011-02-25 16:51           ` debbugs.el Evgeny M. Zubok
2011-03-01 10:15             ` debbugs.el Michael Albinus
2011-03-02 15:56               ` debbugs.el Evgeny M. Zubok
2011-02-25  3:37       ` debbugs.el Lars Ingebrigtsen
2011-02-25  8:17         ` debbugs.el Eli Zaretskii
2011-02-25  8:33           ` debbugs.el Michael Albinus
2011-02-25  8:54             ` debbugs.el Eli Zaretskii
2011-02-25  9:29               ` debbugs.el Miles Bader
2011-02-25  9:55                 ` debbugs.el Eli Zaretskii
2011-02-25 15:43                   ` debbugs.el Stefan Monnier
2011-02-25 15:52                     ` debbugs.el Eli Zaretskii
2011-02-25  9:59           ` Lars Ingebrigtsen [this message]

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

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

  git send-email \
    --in-reply-to=87hbbsxwnq.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=ding@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.
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 NNTP newsgroup(s).