From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: 0.3 and async pre-fetch
Date: 02 Aug 1996 19:35:54 +0200 [thread overview]
Message-ID: <w8s91bx3czp.fsf@hrym.ifi.uio.no> (raw)
In-Reply-To: Sudish Joseph's message of 01 Aug 1996 19:41:35 -0400
Sudish Joseph <sudish@mindspring.com> writes:
> 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?
There was a missing `(goto-char (point-max))' somewhere. The prefetch
seems to work ok in 0.4.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@ifi.uio.no * Lars Ingebrigtsen
next prev parent reply other threads:[~1996-08-02 17:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-08-01 23:41 Sudish Joseph
1996-08-02 1:31 ` 0.3 and async pre-fetch (and YA bug report) Raja R Harinath
1996-08-02 17:35 ` Lars Magne Ingebrigtsen [this message]
1996-08-03 0:35 ` 0.3 and async pre-fetch 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=w8s91bx3czp.fsf@hrym.ifi.uio.no \
--to=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).