From: Arnd Bergmann <arnd@arndb.de>
To: Robin Holt <holt@sgi.com>
Cc: David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, Greg KH <gregkh@suse.de>,
"David S. Miller" <davem@davemloft.net>,
Jens Axboe <axboe@kernel.dk>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 1/8] init: rename CONFIG_EMBEDDED to CONFIG_EXPERT
Date: Thu, 30 Dec 2010 13:50:28 +0100 [thread overview]
Message-ID: <201012301350.28862.arnd@arndb.de> (raw)
In-Reply-To: <20101230124535.GA3306@sgi.com>
On Thursday 30 December 2010, Robin Holt wrote:
> Doesn't this patch series break the 'bisectable' rule for patches?
> I think you can get by with adding a CONFIG_EXPERT selects CONFIG_EMBEDDED
> in the first patch and the last patch removing that same selects.
How about leaving it that way during the merge window even? That would
help people sending git pull requests that add new dependencies on
CONFIG_EMBEDDED. David can submit another patch that removes the
temporary CONFIG_EMBEDDED option along with any new users in -rc2
or for 2.6.39 then.
Arnd
next prev parent reply other threads:[~2010-12-30 12:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-30 4:02 [patch 1/8] init: rename CONFIG_EMBEDDED to CONFIG_EXPERT David Rientjes
2010-12-30 4:02 ` [patch 2/8] arch: " David Rientjes
2010-12-30 4:02 ` [patch 3/8] drivers: " David Rientjes
2010-12-30 4:02 ` [patch 4/8] fs: " David Rientjes
2010-12-30 4:02 ` [patch 5/8] block: " David Rientjes
2010-12-30 4:02 ` [patch 6/8] init: " David Rientjes
2010-12-30 4:02 ` [patch 7/8] lib: " David Rientjes
2010-12-30 4:02 ` [patch 8/8] usr: " David Rientjes
2010-12-30 9:04 ` [patch 1/8] init: " Ingo Molnar
2010-12-30 12:45 ` Robin Holt
2010-12-30 12:50 ` Arnd Bergmann [this message]
2010-12-30 13:10 ` Robin Holt
2010-12-30 19:17 ` David Rientjes
2010-12-30 21:56 ` Valdis.Kletnieks
2011-01-03 20:10 ` Andrew Morton
2011-01-03 21:56 ` David Rientjes
2011-01-02 10:29 ` David Woodhouse
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=201012301350.28862.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=holt@sgi.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rientjes@google.com \
/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