From: carbonated beverage <ramune@net-ronin.org>
To: linux-kernel@vger.kernel.org
Cc: torvalds@transmeta.com
Subject: Re: [PATCH] [TINY] Documentation/Changes for modules
Date: Fri, 27 Dec 2002 13:58:10 -0800 [thread overview]
Message-ID: <20021227215810.GA3809@net-ronin.org> (raw)
In-Reply-To: <20021227200151.GA3469@net-ronin.org>
[-- Attachment #1: Type: text/plain, Size: 202 bytes --]
and here's the incremental patch to fix up references to modules.conf,
conf.moduldes, and kerneld where appropriate to modprobe.conf and kmod.
attatched as a gzip'd file due to the size.
-- dn
daniel
[-- Attachment #2: incremental.patch.gz --]
[-- Type: application/octet-stream, Size: 43195 bytes --]
prev parent reply other threads:[~2002-12-27 21:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-20 19:49 [PATCH] [TINY] Documentation/Changes for modules carbonated beverage
2002-12-27 20:01 ` carbonated beverage
2002-12-27 21:58 ` carbonated beverage [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=20021227215810.GA3809@net-ronin.org \
--to=ramune@net-ronin.org \
--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