From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Maintainer overview
Date: Thu, 28 Jul 2011 10:09:11 +0200 [thread overview]
Message-ID: <m3zkjyakt4.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <E1QmLTB-0001Qq-52@fencepost.gnu.org> (Eli Zaretskii's message of "Thu, 28 Jul 2011 03:57:25 -0400")
Eli Zaretskii <eliz@gnu.org> writes:
> Maybe we should take a step back and talk about the goals of this
> feature. Is this just to be nice to those who don't read
> bug-gnu-emacs and send them a notification? Or do we want to make
> sure every bug is assigned to some "victim"? These are different
> goals, and the solutions are likely to be different.
I was thinking only of the former. In particular, when doing bug triage
it would be nice if debbugs-gnu knew that cperl and org and etc were
primarily handled by people who don't necessarily read emacs-bugs
religiously. I mean, I know the first two, but I don't know "etc". So
having that knowledge in a machine-parseable form would aid bringing a
bug report to the attention of people who knows how to fix the bug.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2011-07-28 8:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 22:48 Maintainer overview Lars Magne Ingebrigtsen
2011-07-28 2:55 ` Eli Zaretskii
2011-07-28 7:35 ` Lars Magne Ingebrigtsen
2011-07-28 7:57 ` Eli Zaretskii
2011-07-28 8:09 ` Lars Magne Ingebrigtsen [this message]
2011-07-28 9:05 ` Eli Zaretskii
2011-07-28 9:08 ` Lars Magne Ingebrigtsen
2011-07-29 2:11 ` Stephen J. Turnbull
2011-07-28 8:48 ` Detlev Zundel
2011-07-28 11:23 ` Juanma Barranquero
2011-07-28 4:47 ` Jambunathan K
2011-07-28 6:14 ` Tim Cross
2011-07-28 7:11 ` Jambunathan K
2011-07-28 7:37 ` Lars Magne Ingebrigtsen
2011-07-28 8:23 ` Tim Cross
2011-07-28 9:04 ` Eli Zaretskii
2011-07-28 8:07 ` Bastien
2011-07-28 16:49 ` Chong Yidong
2011-07-29 11:22 ` Lars Magne Ingebrigtsen
2011-08-02 15:13 ` Stefan Monnier
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=m3zkjyakt4.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=eliz@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.