From: "Paul Rolland" <rol@as2917.net>
To: "'J.A. Magallon'" <jamagallon@able.es>, <linux-kernel@vger.kernel.org>
Subject: Re: [Patch] Kernel configuration in kernel, kernel 2.4.20
Date: Mon, 30 Dec 2002 07:54:55 +0100 [thread overview]
Message-ID: <004f01c2afd0$5ceba280$3f00a8c0@witbe> (raw)
In-Reply-To: <20021229221340.GA2259@werewolf.able.es>
Hello,
> > Tired of keeping copy of the kernel .config file, I decided
> to create
> > a kernel patch to have a /proc/config/config.gz
>
> Why people does not read the archives before doing anything ?
>
Maybe because they consider that there is not only one way to do
things... ;-)
OK, you don't like mine, no problem. I'm just expecting this
functionnality in the kernel, not MY solution.
On a technical basis, I prefer to have a solution that is using
full compression from gzip rather than relying on a set of keyword
that will need to be updated with kernel dev and growth.
But, I'm second...
Regards,
Paul
next prev parent reply other threads:[~2002-12-30 6:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-29 17:08 [Patch] Kernel configuration in kernel, kernel 2.4.20 Paul Rolland
2002-12-29 22:13 ` J.A. Magallon
2002-12-30 6:54 ` Paul Rolland [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-29 23:17 Peter T. Breuer
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='004f01c2afd0$5ceba280$3f00a8c0@witbe' \
--to=rol@as2917.net \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.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