From: Jody Bruchon <jody@jodybruchon.com>
To: ELKS <linux-8086@vger.kernel.org>
Subject: Re: CONFIG_SMALL_KERNEL option added
Date: Mon, 23 Mar 2015 06:43:35 -0400 [thread overview]
Message-ID: <550FEE57.5010806@jodybruchon.com> (raw)
In-Reply-To: <550FEE31.8070903@jodybruchon.com>
On 3/23/2015 4:16 AM, MFLD wrote:
> Reducing the kernel size by making it less verbous looks fine, but I
> think the option is misnamed and that could lead to confusion. A newbie
> like me would understand that option as "reduce the kernel features to
> gain space", not the amount of traces. So I would rename it something
> like "VERBOSE_LESS" ?
The plan is to have the option reduce size in other code as needed, not
just to reduce the number of messages in the kernel.
> Also, could it be possible to make such changes like this latest one in
> another development branch, so that we could have a stable master
> branch, as the official Linux, so that we could review, test, validate
> and mature the changes on our different platforms before merging them ?
ELKS isn't stable enough to justify adding branches for the sake of
having a "stable master" branch. It was only with the release of 0.2.0
that it could be considered remotely close to "stable." Even since then,
I've fixed numerous problems with the code. I'd prefer not to call
anything "stable" until ELKS is at a point that version 1.0 is
justifiable. There are only two people actively working on the ELKS code
base right now, so that's going to take some time.
-Jody
next parent reply other threads:[~2015-03-23 10:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <550FEE31.8070903@jodybruchon.com>
2015-03-23 10:43 ` Jody Bruchon [this message]
2015-03-23 2:21 CONFIG_SMALL_KERNEL option added Jody Bruchon
2015-03-23 8:16 ` MFLD
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=550FEE57.5010806@jodybruchon.com \
--to=jody@jodybruchon.com \
--cc=linux-8086@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).