From: Michal Marek <mmarek@suse.cz>
To: Josh Boyer <jwboyer@redhat.com>
Cc: John Stultz <john.stultz@linaro.org>,
kernel-team@fedoraproject.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] merge_config.sh: Use the first file as the initial config
Date: Sat, 24 Mar 2012 23:26:49 +0100 [thread overview]
Message-ID: <20120324222649.GB8947@sepie.suse.cz> (raw)
In-Reply-To: <20120201170157.GA4907@zod.bos.redhat.com>
On Wed, Feb 01, 2012 at 12:01:58PM -0500, Josh Boyer wrote:
> Take the first config fragment and use it verbatim as the initial config set.
> This avoids running the verification loop for the first file, as nothing has
> actually been merged at this point. This significantly increases performance
> for large config fragments.
>
> Signed-off-by: Josh Boyer <jwboyer@redhat.com>
Applied to kbuild.git#kconfig, thanks.
Michal
prev parent reply other threads:[~2012-03-24 22:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 17:01 Josh Boyer
2012-02-02 20:14 ` John Stultz
2012-02-02 20:37 ` Darren Hart
2012-03-24 22:26 ` Michal Marek [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=20120324222649.GB8947@sepie.suse.cz \
--to=mmarek@suse.cz \
--cc=john.stultz@linaro.org \
--cc=jwboyer@redhat.com \
--cc=kernel-team@fedoraproject.org \
--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
all inboxes | Powered by JetHome®