From: Alan Shutko <ats@acm.org>
Subject: Re: Gnus development remains haphazard?
Date: Wed, 28 Mar 2001 19:15:52 -0500 [thread overview]
Message-ID: <87puf1whw0.fsf@wesley.springies.nom> (raw)
In-Reply-To: <m21yrhv63b.fsf@swift.shore.net>
Matt Swift <swift@alum.mit.edu> writes:
> I don't have the resources or knowledge to establish a bug tracking
> system,
Both sourceforge and savannah do, though. It might be useful to start
taking advantage of some of their tools.
--
Alan Shutko <ats@acm.org> - In a variety of flavors!
With your bare hands?!?
next prev parent reply other threads:[~2001-03-29 0:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-28 23:14 Matt Swift
2001-03-29 0:15 ` Alan Shutko [this message]
2001-03-29 5:57 ` William M. Perry
2001-04-02 10:58 ` Matt Swift
2001-04-02 11:29 ` Kai Großjohann
2001-04-02 13:33 ` 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=87puf1whw0.fsf@wesley.springies.nom \
--to=ats@acm.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).