From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Cc: ding@gnus.org
Subject: Re: can Gnus simply use the Emacs bug tracker?
Date: Wed, 16 Mar 2011 13:44:05 -0500 [thread overview]
Message-ID: <8739mmvrbe.fsf@lifelogs.com> (raw)
In-Reply-To: <m339mnc6ox.fsf@quimbies.gnus.org>
On Wed, 16 Mar 2011 18:32:14 +0100 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
LMI> Or perhaps we could just remove `M-x gnus-bug' from the version in the
LMI> trunk, and tell people to report the bugs the normal way?
LMI> Alternatively, define `M-x gnus-bug' as an alias to `M-x
LMI> report-emacs-bugs'. Perhaps with the extra package thing?
I think the second way is better, yes, so we can customize `gnus-bug'
as needed.
On Wed, 16 Mar 2011 13:55:33 -0400 Glenn Morris <rgm@gnu.org> wrote:
GM> Glenn Morris wrote (on Wed, 16 Mar 2011 at 13:51 -0400):
>> Yes, I suggest you make M-x gnus-bug always send mail to bug-gnu-emacs.
>> The only difference should be that in standalone Gnus, you add a line
>> "Package: gnus" at the start of the body, whereas in Emacs you add
>> "Package: emacs,gnus".
GM> The only difficulty is you need to document that bug reports will end
GM> up at different addresses based on the package line. Maybe it's better
GM> to send the mail to submit@debbugs rather than bug-gnu-emacs. It
GM> doesn't affect how anything works, but it might make people a bit less
GM> likely to say "why isn't my report showing up on bug-gnu-emacs?"
So M-x gnus-bug will: 1) send to submit@debbugs, and 2) set the Package
to either "gnus" in a Gnus checkout, or "emacs,gnus" in a trunk
checkout. No mail server reconfiguration will be necessary.
Ted
next prev parent reply other threads:[~2011-03-16 18:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 16:38 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 [this message]
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 19:12 ` Ted Zlatanov
[not found] ` <3tmxkty6up.fsf@fencepost.gnu.org>
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-06-28 15:33 ` Ted Zlatanov
2011-03-15 20:31 ` Chong Yidong
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8739mmvrbe.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).