From: Eli Zaretskii <eliz@gnu.org>
To: Miles Bader <miles@gnu.org>
Cc: michael.albinus@gmx.de, larsi@gnus.org, ding@gnus.org,
emacs-devel@gnu.org
Subject: Re: debbugs.el
Date: Fri, 25 Feb 2011 11:55:40 +0200 [thread overview]
Message-ID: <83pqqgqvz7.fsf@gnu.org> (raw)
In-Reply-To: <buor5aw8nt6.fsf@dhlpc061.dev.necel.com>
> From: Miles Bader <miles@gnu.org>
> Cc: Michael Albinus <michael.albinus@gmx.de>, larsi@gnus.org, ding@gnus.org,
> emacs-devel@gnu.org
> Date: Fri, 25 Feb 2011 18:29:25 +0900
>
> > I'm all for it, mind you. I just think that the reasons stated by
> > Lars are not a valid justification for having such an interface in
> > Emacs.
>
> "I'd be checking it a lot more often" seems like pretty good
> justification to me...
?? 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?
Querying the database when actually _working_ on bugs is another
matter, and that is IMO the real reason for having this interface.
But just to know that a bug related to one's work or interests exist,
you can easily do with the mailing list.
next prev parent reply other threads:[~2011-02-25 9:55 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 ` Eli Zaretskii [this message]
2011-02-25 15:43 ` debbugs.el Stefan Monnier
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=83pqqgqvz7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=ding@gnus.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).