From: Andrew Morton <akpm@osdl.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm] Bisecting through -mm with quilt
Date: Thu, 22 Sep 2005 17:42:50 -0700 [thread overview]
Message-ID: <20050922174250.71f9c6a9.akpm@osdl.org> (raw)
In-Reply-To: <20050923003217.GA18675@mipter.zuzino.mipt.ru>
Alexey Dobriyan <adobriyan@gmail.com> wrote:
>
> Quick, Dirty, Fragile, Should Work (TM).
hm, I wouldn't use it. The problem is that a _lot_ of patches in -mm don't
fscking compile.
bix:/usr/src/25> grep '[-]fix.patch' series | wc
72 72 2905
If your bisection happens to land you between foo.patch and foo-fix.patch,
you have a *known bad* kernel. What's the point in testing it?
So I'd recommend the smarter approach: copy the series file to ~/hunt, edit
~/hunt and do the bisection by hand, marking the good and bad points in
~/hunt as you go.
next prev parent reply other threads:[~2005-09-23 0:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-23 0:32 [PATCH -mm] Bisecting through -mm with quilt Alexey Dobriyan
2005-09-23 0:42 ` Andrew Morton [this message]
2005-09-23 15:20 ` [PATCH -mm v2] " Alexey Dobriyan
2005-09-23 15:33 ` Alexey Dobriyan
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=20050922174250.71f9c6a9.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=adobriyan@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).