From: srivasta@pilgrim.umass.edu
Subject: Re: September Gnus 0.31 is released
Date: Thu, 25 Jan 1996 18:54:14 -0500 (EST) [thread overview]
Message-ID: <199601252354.SAA01433@belthil.pilgrim.umass.edu> (raw)
In-Reply-To: <w8sohrsuuix.fsf@aegir.ifi.uio.no>
Hi,
I finally implemented a real mirror of
<URL:ftp://ftp.ifi.uio.no/pub/emacs/gnus/>, so now my site should
always have the latest version within 24 hours, connectivity
permitting. I'll continue to grab the patches over by hand.
Since I am now a real mirror, and I believe mentioned in the
FAQ, I'll stop taking up bandwidth on this mailing list with these
annoncements.
Now also at:
<URL: ftp://ftp.pilgrim.umass.edu/pub/misc/ding/>
<URL: http://www.pilgrim.umass.edu/pub/misc/ding/>
<URL: gopher://gopher.pilgrim.umass.edu/11/pub/misc/ding/>
Currently on tap:
total 2926
8 ./ 8 refcard/
8 ../ 8 s-manual/
74 .mirror 7 sgnus-0.25-0.26.diff.gz
0 FAQ@ 208 sgnus-0.26-0.27.diff.gz
6 dgnus-5.0.12-5.0.13.diff.gz 21 sgnus-0.27-0.28.diff.gz
40 etc-0.4.tar.gz 3 sgnus-0.28-0.29.diff.gz
0 etc.tar.gz@ 23 sgnus-0.29-0.30.diff.gz
8 faq/ 48 sgnus-0.30-0.31.diff.gz
416 gnus-5.0.13.tar.gz 520 sgnus-0.31.tar.gz
0 gnus.tar.gz@ 0 sgnus.tar.gz@
1336 icons.tar.gz 176 tm7.41.tar.gz
8 manual/
ding/faq:
total 349
8 ./ 23 gnus-faq 280 gnus-faq.ps
8 ../ 30 gnus-faq.html
ding/manual:
total 400
8 ./ 2 gnus_10.html 5 gnus_2.html 6 gnus_7.html
8 ../ 2 gnus_11.html 18 gnus_3.html 11 gnus_8.html
2 .cache 26 gnus_12.html 74 gnus_4.html 6 gnus_9.html
4 .cache+ 46 gnus_13.html 128 gnus_5.html 10 gnus_toc.html
17 gnus_1.html 17 gnus_14.html 10 gnus_6.html
ding/refcard:
total 291
8 ./ 32 bk-a4-s1.ps.gz 20 gnusref.tar.gz
8 ../ 26 bk-a4-s2.ps.gz 21 quickref.ps.gz
1 .cache 40 bk-lt-d.ps.gz 34 refcard.ps.gz
3 README 32 bk-lt-s1.ps.gz
40 bk-a4-d.ps.gz 26 bk-lt-s2.ps.gz
ding/s-manual:
total 582
8 ./ 2 gnus_12.html 23 gnus_3.html 37 gnus_8.html
8 ../ 56 gnus_13.html 112 gnus_4.html 27 gnus_9.html
17 gnus_1.html 64 gnus_14.html 160 gnus_5.html 13 gnus_toc.html
6 gnus_10.html 21 gnus_15.html 12 gnus_6.html
3 gnus_11.html 5 gnus_2.html 8 gnus_7.html
manoj
--
There ain't nothin' in this world that's worth being a snot over.
--Larry Wall in <1992Aug19.041614.6963@netlabs.com> %%
Manoj Srivastava Systems Research Programmer, Project Pilgrim,
Phone: (413) 545-3918 A143B Lederle Graduate Research Center,
Fax: (413) 545-1249 University of Massachusetts, Amherst, MA 01003
<srivasta@pilgrim.umass.edu> <URL:http://www.pilgrim.umass.edu/%7Esrivasta/>
next prev parent reply other threads:[~1996-01-25 23:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-01-25 16:12 Lars Magne Ingebrigtsen
1996-01-25 18:36 ` Steven L Baur
1996-01-25 21:50 ` Wes Hardaker
1996-01-25 22:44 ` luis fernandes
1996-01-26 1:07 ` Steven L Baur
1996-01-26 15:28 ` Colin Rafferty
1996-01-26 17:47 ` Wes Hardaker
1996-01-26 17:48 ` Steven L Baur
1996-01-27 20:33 ` Lars Magne Ingebrigtsen
1996-01-26 16:46 ` Lars Magne Ingebrigtsen
1996-01-26 17:37 ` Steven L Baur
1996-01-27 20:33 ` Lars Magne Ingebrigtsen
1996-01-28 0:13 ` Steven L Baur
1996-01-30 16:29 ` Lars Magne Ingebrigtsen
1996-01-25 23:54 ` srivasta [this message]
1996-01-26 19:33 ` Mark Borges
1996-01-26 20:28 ` Steven L Baur
1996-01-26 20:29 ` Manoj Srivastava
1996-01-26 20:39 ` Colin Rafferty
1996-01-26 20:50 ` Mark Borges
1996-01-26 23:17 ` Steven L Baur
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=199601252354.SAA01433@belthil.pilgrim.umass.edu \
--to=srivasta@pilgrim.umass.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).