From: "boyd, rounin" <boyd@insultant.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] webcookies translator?
Date: Thu, 12 Jun 2003 19:58:06 +0200 [thread overview]
Message-ID: <016701c3310c$2d903560$e3944251@insultant.net> (raw)
In-Reply-To: <af3f3e2ef3d7bca271b79e345fd32f10@plan9.bell-labs.com>
> i can't fault them for not documenting
> one of their internal files in a system that
> isn't meant for users to be looking at those
> files anyway.
well i can. even when they do document stuff it's written in a style of:
- it does X
- except in the case of Y
- it does not X
X & Y are verbose to the point of unintelligibility.
so you just gotta figure it out :(
prev parent reply other threads:[~2003-06-12 17:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-12 16:22 steve.simon
2003-06-12 16:30 ` matt
2003-06-12 16:35 ` boyd, rounin
2003-06-12 17:36 ` Russ Cox
2003-06-12 17:47 ` boyd, rounin
2003-06-12 17:51 ` Russ Cox
2003-06-12 17:58 ` boyd, rounin [this message]
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='016701c3310c$2d903560$e3944251@insultant.net' \
--to=boyd@insultant.net \
--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).