From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, emacs-devel@gnu.org, michael.albinus@gmx.de,
ding@gnus.org, Miles Bader <miles@gnu.org>
Subject: Re: debbugs.el
Date: Fri, 25 Feb 2011 10:43:06 -0500 [thread overview]
Message-ID: <jwvipw89l5a.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83pqqgqvz7.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 25 Feb 2011 11:55:40 +0200")
> ?? If you are subscribed to the mailing list, the bugs are already in
> your mailbox. So why would you need to "check" debbugs, just to know
> about their existence?
For Emacs maintainers, that's mostly true, but for maintainers of some
particular (set of) packages, it's not so easy: reports that interest
them can get drowned in the rest.
Stefan
next prev parent reply other threads:[~2011-02-25 15:43 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 ` Stefan Monnier [this message]
2011-02-25 15:52 ` debbugs.el Eli Zaretskii
2011-02-25 9:59 ` debbugs.el Lars Ingebrigtsen
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=jwvipw89l5a.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=ding@gnus.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=michael.albinus@gmx.de \
--cc=miles@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).