From: Rajappa Iyer <rsi@lucent.com>
Cc: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: Red Gnus v0.81 is released
Date: 15 Jan 1997 08:26:33 -0500 [thread overview]
Message-ID: <199701151326.IAA09883@fragola.hr.lucent.com> (raw)
In-Reply-To: <m2oherk165.fsf@proletcult.slip.ifi.uio.no>
Suggestion:
I'm not sure if this was ever discussed before in the mailing list,
but given the frequency of Red Gnus releases, it might be a good idea
to also post patches... either on the mailing list or at the ftp site.
It's kind of painful to have to download 736Kb or so every time,
especially if you have a slow link.
What do people think?
Rajappa
--
Rajappa Iyer <rsi@lucent.com> #include <std_disclaimer.h>
They also surf who only stand on the waves.
next prev parent reply other threads:[~1997-01-15 13:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-01-15 4:33 Lars Magne Ingebrigtsen
1997-01-15 13:26 ` Rajappa Iyer [this message]
1997-01-15 15:01 ` William M. Perry
1997-01-15 21:46 ` Jason L Tibbitts III
1997-01-16 8:51 ` Johan Danielsson
1997-01-16 11:21 ` Robert Bihlmeyer
1997-01-16 23:06 ` Lars Magne Ingebrigtsen
1997-01-15 21:21 ` Possible bug in 0.81 David Watson
1997-01-15 21:54 ` Steven L Baur
1997-01-15 22:12 ` Katsumi Yamaoka
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=199701151326.IAA09883@fragola.hr.lucent.com \
--to=rsi@lucent.com \
--cc=larsi@ifi.uio.no \
/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).