linux-kernel - Re: [patch 1/8] init: rename CONFIG_EMBEDDED to CONFIG

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20101230131031.GF3260@sgi.com>
Date:	Thu, 30 Dec 2010 07:10:31 -0600
From:	Robin Holt <holt@....com>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Robin Holt <holt@....com>, David Rientjes <rientjes@...gle.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>, Greg KH <gregkh@...e.de>,
	"David S. Miller" <davem@...emloft.net>,
	Jens Axboe <axboe@...nel.dk>, linux-arch@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [patch 1/8] init: rename CONFIG_EMBEDDED to CONFIG_EXPERT

On Thu, Dec 30, 2010 at 01:50:28PM +0100, Arnd Bergmann wrote:
> 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.

That would be fine with me, but I don't think my vote counts for much.
I was just trying to help prevent the bisectability of your patchset.

Robin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/