From: Dana Lacoste <dana.lacoste@peregrine.com>
To: "'Alan Cox'" <alan@lxorguk.ukuu.org.uk>
Cc: kaboom@gatech.edu, torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: RE: ANOTHER modest proposal -- We need a documentation package
Date: Wed, 30 Jan 2002 07:23:40 -0800 [thread overview]
Message-ID: <B51F07F0080AD511AC4A0002A52CAB445B2B2C@ottonexc1.ottawa.loran.com> (raw)
> Its then permanently out of date, and you can't keep the two
> tied together.
but from what was said, Linus isn't keeping them up to date
anyways, so how would this be _worse_?
next reply other threads:[~2002-01-30 15:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-30 15:23 Dana Lacoste [this message]
2002-01-30 16:29 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2002-01-30 15:03 Dana Lacoste
2002-01-30 15:34 ` Alan Cox
2002-01-30 16:25 ` Jeff Garzik
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=B51F07F0080AD511AC4A0002A52CAB445B2B2C@ottonexc1.ottawa.loran.com \
--to=dana.lacoste@peregrine.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=kaboom@gatech.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®