From: Tomas Szepe <szepe@pinerecords.com>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: more thoughts on kernel config organization
Date: Sun, 12 Jan 2003 11:03:35 +0100 [thread overview]
Message-ID: <20030112100335.GE11450@louise.pinerecords.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0301120421010.24231-100000@dell>
> [rpjday@mindspring.com]
>
> a couple hours ago, i posted an alternate fs/Kconfig file, but i haven't
> seen it appear on the mailing list. is there a size limit for postings?
> is there another way to make it available for anyone who wants to check
> it out?
Make the re-arranged Kconfig a unidiff against latest bk, check that
everything compiles as expected and send it here. If the diff turns
out large (it probably will), gzip it.
--
Tomas Szepe <szepe@pinerecords.com>
next prev parent reply other threads:[~2003-01-12 9:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-12 4:17 more thoughts on kernel config organization Robert P. J. Day
2003-01-12 8:04 ` Sam Ravnborg
2003-01-12 9:22 ` Robert P. J. Day
2003-01-12 10:03 ` Tomas Szepe [this message]
2003-01-12 17:12 ` Roman Zippel
2003-01-13 12:32 ` Dave Jones
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=20030112100335.GE11450@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.com \
--cc=sam@ravnborg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.