From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Ingo Molnar <mingo@elte•hu>
Cc: Randy Dunlap <randy.dunlap@oracle•com>,
linux-next@vger•kernel.org, lkml <linux-kernel@vger•kernel.org>,
mingo <mingo@redhat•com>, tglx <tglx@linutronix•de>,
hpa <hpa@zytor•com>, akpm <akpm@linux-foundation•org>,
Jens Axboe <jens.axboe@oracle•com>
Subject: Re: [PATCH -next] fork and exit: need to include iocontext.h
Date: Tue, 1 Jul 2008 10:34:17 +1000 [thread overview]
Message-ID: <20080701103417.c0c09538.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20080630183337.GD32211@elte.hu>
[-- Attachment #1: Type: text/plain, Size: 754 bytes --]
On Mon, 30 Jun 2008 20:33:37 +0200 Ingo Molnar <mingo@elte•hu> wrote:
>
> normally there's an easy way to find out the source commit of build
> failures. Try something like:
>
> git-bisect reset
> git-bisect start
> git-bisect good v2.6.26-rc8
More generally "git-bisect good linux-next/stable" - the stable branch is
just where I started on Linus' tree and that is always good :-)
> git-bisect bad linux-next/master
> git-bisect run make kernel/fork.o
>
> ... this should lead you to the commit that broke the build
> automatically. (as long as everyone keeps make oldconfig compatibility)
Nice, I must try this.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-07-01 0:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-30 17:54 [PATCH -next] fork and exit: need to include iocontext.h Randy Dunlap
2008-06-30 18:05 ` Ingo Molnar
2008-06-30 18:22 ` Randy Dunlap
2008-06-30 18:33 ` Ingo Molnar
2008-06-30 18:39 ` Randy Dunlap
2008-06-30 18:47 ` Ingo Molnar
2008-07-01 0:34 ` Stephen Rothwell [this message]
2008-06-30 18:38 ` Jens Axboe
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=20080701103417.c0c09538.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=hpa@zytor$(echo .)com \
--cc=jens.axboe@oracle$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@elte$(echo .)hu \
--cc=mingo@redhat$(echo .)com \
--cc=randy.dunlap@oracle$(echo .)com \
--cc=tglx@linutronix$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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