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: Tue, 15 Mar 2011 13:27:29 -0500 [thread overview]
Message-ID: <87r5a8z1bi.fsf@lifelogs.com> (raw)
In-Reply-To: <874o748epu.fsf@stupidchicken.com>
On Tue, 15 Mar 2011 13:40:13 -0400 Chong Yidong <cyd@stupidchicken.com> wrote:
CY> Ted Zlatanov <tzz@lifelogs.com> writes:
>> This would involve changes to `M-x gnus-bug' and the Gnus manual.
CY> I don't think such a change would involve changes to gnus-bug.
Well, if the tracker wanted to have extra information in the message
headers... I thought it would be necessary.
CY> Have you read the "Using the GNU Bug Tracker" page that Glenn Morris
CY> wrote?
CY> http://debbugs.gnu.org/Using.html
CY> As explained there, the usual way to use the Emacs bug tracker is for it
CY> to take over bugs@gnus.org.
Thank you for the reference, I had not seen it.
It seems the alias list on the bug tracker needs to be updated but
otherwise this can be pretty seamless on both sides, besides the
potential problem below.
CY> One problem, though, is that up to now we've only ever set up the bug
CY> tracker for @gnu.org mailing lists. ISTR that the list traffic is
CY> redirected to debbugs.gnu.org simply via a rule in the FSF mail server,
CY> which might not work for handling a non-gnu.org list. Glenn, do you
CY> recall the details?
On the Gnus side we can change the bugs@gnus.org alias as needed, of course.
Ted
next prev parent reply other threads:[~2011-03-15 18:27 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 [this message]
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 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=87r5a8z1bi.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).