From: Martin C.Atkins <martin@mca-ltd.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] debugmalloc
Date: Mon, 5 Aug 2002 11:34:08 +0100 [thread overview]
Message-ID: <20020805113408.693059cc.martin@mca-ltd.com> (raw)
In-Reply-To: <45018e4df46ea03b067ec05331ebfa9e@caldo.demon.co.uk>
On Sun, 4 Aug 2002 17:54:42 +0100 forsyth@caldo.demon.co.uk wrote:
> printed 4th edition manuals are indeed snapshots. i'd have preferred
> to print on dynamic paper(tm), but it isn't available yet.
>
Wouldn't that suffer from the "I'm sure I read X, but I can't find it anywhere"
problem :-)?
Martin
--
Martin C. Atkins martin@mca-ltd.com
Mission Critical Applications Ltd, U.K.
next prev parent reply other threads:[~2002-08-05 10:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-04 16:54 forsyth
2002-08-05 10:34 ` Martin C.Atkins [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-04 13:58 rob pike, esq.
2002-08-04 13:36 Russ Cox
2002-08-04 7:44 matt
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=20020805113408.693059cc.martin@mca-ltd.com \
--to=martin@mca-ltd.com \
--cc=9fans@cse.psu.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).