From: Sudish Joseph <sudish@mindspring.com>
Subject: 0.3 and async pre-fetch
Date: 01 Aug 1996 19:41:35 -0400 [thread overview]
Message-ID: <m2spa6ekpc.fsf@atreides.erehwon.org> (raw)
I'm curious, why isn't anyone else reporting this? Is it that the
bug is only visible over a slow connect? Has anyone else seen this?
It's still got the problem that I sent in the patch for. Here's what
I see.
I snipped the beginning of this article (the article I was actually
reading).
--------------------------------------------------
Eh, the UNIX biggots won't flame you for porting a _client_. If you
really want to piss them off, though, port the server next. ;-)
Regards,
Andy
--
_____________________________________________________________________________
Andy Gough | "Knowledge is power."
Internet: agough@primenet.com | -- Francis Bacon
ICBM: 33^18'29" N 111^48'39" W | PGP Key: finger agough@primenet.com
-----------------------------------------------------------------------------
.
220 56134 <bluddoDvG08y.5wu@netcom.com> article
Newsgroups: rec.games.netrek
[ snipped the rest of the nntp results from 6 articles ]
netrek ftp site: ftp.best.com /pub/doosh/netrek
netrek home page: http://www.isn.net/~farnorth/netrek.html
.
200 news.mindspring.com InterNetNews NNRP server INN 1.4 22-Dec-93 ready (posting ok).
--------------------------------------------------
-Sudish
next reply other threads:[~1996-08-01 23:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-08-01 23:41 Sudish Joseph [this message]
1996-08-02 1:31 ` 0.3 and async pre-fetch (and YA bug report) Raja R Harinath
1996-08-02 17:35 ` 0.3 and async pre-fetch Lars Magne Ingebrigtsen
1996-08-03 0:35 ` Sudish Joseph
1996-08-04 22:09 ` [ patch ] async stuff fix(?) (was Re: 0.3 and async pre-fetch) Sudish Joseph
1996-08-05 0:39 ` Sudish Joseph
1996-08-05 17:11 ` Lars Magne Ingebrigtsen
1996-08-06 6:08 ` Sudish Joseph
1996-08-06 20:51 ` Lars Magne Ingebrigtsen
1996-08-05 18:20 ` Ken Raeburn
1996-08-05 17:00 ` 0.3 and async pre-fetch 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=m2spa6ekpc.fsf@atreides.erehwon.org \
--to=sudish@mindspring.com \
/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).