[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdWq+NntrPqMHzP3XEvKZgjEwSHW80vwWkZnaTORRrhpHA@mail.gmail.com>
Date: Tue, 4 Oct 2022 11:20:32 +0200
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Thorsten Leemhuis <linux@...mhuis.info>
Cc: Steven Rostedt <rostedt@...dmis.org>,
Slade Watkins <srw@...dewatkins.net>,
Konstantin Ryabitsev <konstantin@...uxfoundation.org>,
"Artem S. Tashkinov" <aros@....com>, workflows@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"regressions@...ts.linux.dev" <regressions@...ts.linux.dev>,
ksummit@...ts.linux.dev
Subject: Re: Planned changes for bugzilla.kernel.org to reduce the "Bugzilla blues"
Hi Thorsten,
On Tue, Oct 4, 2022 at 10:41 AM Thorsten Leemhuis <linux@...mhuis.info> wrote:
> But I consider explaining things like bisection and localmodconfig in
> the documentation as also important, as that's likely something the tool
> won't be able to automate any time soon (or never, as realizing that is
> likely hard and better left to a separate tool anyway).
Creating a simple Linux-specific wrapper around git bisect under
scripts/ might be useful?
The wrapper could copy .config to
$(srctree)/arch/$(ARCH)/config/bisect_defconfig, automatically run
"make bisect_defconfig" in each step, and show not only the bisected
commit, but also the impact on .config.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Powered by blists - more mailing lists