From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Who reads the gnus bugs list
Date: 12 May 2000 12:00:16 -0400 [thread overview]
Message-ID: <2nln1f92sv.fsf@tiger.jia.vnet> (raw)
In-Reply-To: Simon Josefsson's message of "12 May 2000 13:14:40 +0200"
>>>>> "Simon" == Simon Josefsson <jas@pdc.kth.se> writes:
Simon> Steinar Bang <sb@metis.no> writes:
>> Who reads the Gnus bugs list these days? Just larsi (when he has
>> the time)? Or others like Simon and Shenghuo also read it?
Simon> I do, but I've had little time to reply.
I read it and fix some bugs if I got time.
>> Ie. should one report bugs and bug fixes to gnus-bugs or to the
>> ding mailing list?
Simon> IMHO:
Simon> This is the developer list, so any recently introduced bugs
Simon> should probably be discussed here so they can be fixed (like
Simon> the URL regexp thingie).
Simon> Other, boring (long-standing, low-priority, bugs with attached
Simon> fix, etc) bug reports could go to bugs@gnus.org.
Bug reports with large attachments (for reproducing) should go to
bugs@gnus.org too.
Shenghuo
prev parent reply other threads:[~2000-05-12 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-12 8:01 Steinar Bang
2000-05-12 11:14 ` Simon Josefsson
2000-05-12 16:00 ` Shenghuo ZHU [this message]
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=2nln1f92sv.fsf@tiger.jia.vnet \
--to=zsh@cs.rochester.edu \
/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).