From: Maksim Krasnyanskiy <maxk@qualcomm.com>
To: "Dunlap, Randy" <randy.dunlap@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: RE: Undocumented configuration symbols in 2.4.6pre2
Date: Wed, 13 Jun 2001 13:51:27 -0700 [thread overview]
Message-ID: <4.3.1.0.20010613134811.020995d0@mail1> (raw)
In-Reply-To: <D5E932F578EBD111AC3F00A0C96B1E6F07DBE32F@orsmsx31.jf.intel .com>
Randy,
>Could you make these 5 instances of "Not unsure" be more palatable and less confusing ?
Oops, blind cut&past without reading carefully :).
Thanks
Max
Maksim Krasnyanskiy
Senior Kernel Engineer
Qualcomm Incorporated
maxk@qualcomm.com
(408) 557-1092
next parent reply other threads:[~2001-06-13 20:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <D5E932F578EBD111AC3F00A0C96B1E6F07DBE32F@orsmsx31.jf.intel .com>
2001-06-13 20:51 ` Maksim Krasnyanskiy [this message]
2001-06-13 20:19 Undocumented configuration symbols in 2.4.6pre2 Dunlap, Randy
-- strict thread matches above, loose matches on Subject: below --
2001-06-10 14:09 Eric S. Raymond
2001-06-13 19:35 ` Maksim Krasnyanskiy
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=4.3.1.0.20010613134811.020995d0@mail1 \
--to=maxk@qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@intel.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).