From: Chong Yidong <cyd@stupidchicken.com>
To: Glenn Morris <rgm@gnu.org>
Cc: Ted Zlatanov <tzz@lifelogs.com>, ding@gnus.org, emacs-devel@gnu.org
Subject: Re: can Gnus simply use the Emacs bug tracker?
Date: Tue, 15 Mar 2011 16:31:40 -0400 [thread overview]
Message-ID: <87r5a8azwz.fsf@stupidchicken.com> (raw)
In-Reply-To: <6iy64gxk4z.fsf@fencepost.gnu.org> (Glenn Morris's message of "Tue, 15 Mar 2011 15:23:56 -0400")
Glenn Morris <rgm@gnu.org> writes:
> So really all that is needed is to use "Package: gnus" in the first
> line of a mail to submit@debbugs. Using "Package: emacs,gnus" causes
> both bugs@gnus.org and bug-gnu-emacs to get mails. You can do this
> today with zero other changes required.
This would be easier than trying to figure out the correct mail rules to
take over bug@gnus.org, indeed.
The disadvantage is that the Gnus project will get a mix of tracked and
untracked bugs, since many existing users would still report bugs to the
"unmanaged" bugs@gnus.org.
> With regards to making it more "official", personally I hesitate a
> bit. debbugs.gnu.org is a GNU machine and the set-up is intended for
> GNU projects. Do you regard Gnus as a GNU project? GNU Gnus? I know
> Gnus is part of Emacs, but eg
>
> http://www.gnu.org/software/gnus
>
> does not exist, and I don't seem to find a statement on
> http://www.gnus.org/. There don't seem to be any mentions in the Gnus
> manual either.
The VM was originally provided to us as a bug tracker for Emacs, not as
a GNU bug server; so as far as I'm concerned we have a broad mandate for
using it to manage Emacs-related bugs. We can give the FSF a heads-up,
but frankly I don't see this issue being a problem.
next prev parent reply other threads:[~2011-03-15 20:31 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 16:38 can Gnus simply use the Emacs bug tracker? Ted Zlatanov
2011-03-15 17:40 ` Chong Yidong
2011-03-15 18:27 ` Ted Zlatanov
2011-03-15 19:32 ` Glenn Morris
2011-03-15 19:08 ` Stefan Monnier
2011-03-15 19:23 ` Glenn Morris
2011-03-15 19:41 ` Lars Magne Ingebrigtsen
2011-03-15 19:47 ` Ted Zlatanov
2011-03-15 23:27 ` Glenn Morris
2011-03-16 14:00 ` Ted Zlatanov
2011-03-16 15:41 ` Stefan Monnier
2011-03-16 15:58 ` Ted Zlatanov
2011-03-16 17:51 ` Glenn Morris
2011-03-16 17:55 ` Glenn Morris
2011-03-16 19:41 ` Stefan Monnier
2011-03-16 17:32 ` Lars Magne Ingebrigtsen
2011-03-16 18:44 ` Ted Zlatanov
2011-03-17 16:52 ` Lars Magne Ingebrigtsen
2011-03-17 17:27 ` Ted Zlatanov
2011-03-17 17:40 ` Lars Magne Ingebrigtsen
2011-03-17 17:50 ` Glenn Morris
2011-03-17 17:53 ` Glenn Morris
2011-03-18 8:33 ` Reiner Steib
2011-03-18 13:04 ` Ted Zlatanov
2011-03-29 18:53 ` Lars Magne Ingebrigtsen
2011-03-29 19:09 ` Ted Zlatanov
2011-06-28 15:31 ` Ted Zlatanov
2011-03-17 19:12 ` Ted Zlatanov
2011-06-28 15:33 ` Ted Zlatanov
2011-03-15 20:31 ` Chong Yidong [this message]
2011-03-15 20:45 ` Lars Magne 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
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=87r5a8azwz.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=rgm@gnu.org \
--cc=tzz@lifelogs.com \
/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).