linux-kernel - Re: [PATCH 0/6] menuconfig: jump to search results

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: <20120730202212.GA31790@d2.synalogic.ca>
Date:	Mon, 30 Jul 2012 16:22:12 -0400
From:	Benjamin Poirier <bpoirier@...e.de>
To:	Borislav Petkov <bp@...en8.de>, Michal Marek <mmarek@...e.cz>,
	Lucas De Marchi <lucas.demarchi@...fusion.mobi>,
	Arnaud Lacombe <lacombar@...il.com>,
	linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org,
	Randy Dunlap <rdunlap@...otime.net>
Subject: Re: [PATCH 0/6] menuconfig: jump to search results

On 2012/07/30 21:58, Borislav Petkov wrote:
> On Mon, Jul 30, 2012 at 03:22:04PM -0400, Benjamin Poirier wrote:
> > Hello,
> > 
> > This patch series adds "jump to" keys (similar to the cscope interface) to the
> > search results of "make menuconfig" so that we can go directly to the menu
> > entry for a config option after searching for it.
> > 
> > Patches 1-4 implement the basic functionnality.
> > Patches 5-6 are an optionnal improvement.
> 
> Generally,
> 
> a nice idea, I like it.
> 
> A couple of notes though:
> 
> * patches 2/6 and 3/6 don't have commit messages and it would be good if
> they had, even though it is obvious what the changes in there do.
> 
> * this patchset must be against some kbuild tree because it doesn't
> apply against 3.5:

It's against linux-next, which already contains some patches for
menuconfig.
--
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/