From: Tomas Szepe <szepe@pinerecords.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.72 insmod question
Date: Fri, 18 Jul 2003 13:50:45 +0200 [thread overview]
Message-ID: <20030718115045.GW8160@louise.pinerecords.com> (raw)
In-Reply-To: <1173.4.4.25.4.1058489266.squirrel@www.osdl.org>
> [rddunlap@osdl.org]
>
> And you probably should read over the 2.6 migration document:
> http://www.codemonkey.org.uk/post-halloween-2.5.txt
Wouldn't it be a good idea to print a similar note during
"make *config" in the 2.6.0-test series? I mean, this must
be the 80th or so post of its kind this week.
--
Tomas Szepe <szepe@pinerecords.com>
next prev parent reply other threads:[~2003-07-18 11:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-18 0:35 yiding_wang
2003-07-18 0:47 ` Randy.Dunlap
2003-07-18 11:50 ` Tomas Szepe [this message]
2003-07-18 14:35 ` Randy.Dunlap
2003-07-18 22:53 ` Ronald Jerome
2003-07-18 9:59 ` Cesar Suga
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=20030718115045.GW8160@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
/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®