git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Antriksh Pany <antriksh.pany@gmail.com>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: Michael Witten <mfwitten@gmail.com>, git <git@vger.kernel.org>
Subject: Re: Patching bad commits
Date: Mon, 5 Jul 2010 14:07:20 +0530	[thread overview]
Message-ID: <AANLkTilrvCyCCIlU9M1HPAdxLREvyVL0pKyNsJR2wpN7@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimAAtO9p2rQW4pITKQehhYF6pppBUgPxoyrLOvA@mail.gmail.com>

On Tue, Jun 29, 2010 at 3:53 AM, Avery Pennarun <apenwarr@gmail.com> wrote:
> On Mon, Jun 28, 2010 at 6:03 PM, Michael Witten <mfwitten@gmail.com> wrote:
>> Sometimes bisecting is less than useful because a number of commits
>> fail to build.
>>

You could automate the process of skipping certain commits when build fails.
  make || git bisect skip
Automatically mark commits as bad when your test fails:
  ./test || git bisect bad
Otherwise 'git bisect good' is what you do.

I think you can put these together in a loop that works automatically
without much user intervention.

Hope this helps.

Cheers
Antriksh Pany

  reply	other threads:[~2010-07-05  8:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-28 22:03 Patching bad commits Michael Witten
2010-06-28 22:23 ` Avery Pennarun
2010-07-05  8:37   ` Antriksh Pany [this message]
2010-06-28 22:24 ` Sverre Rabbelier

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=AANLkTilrvCyCCIlU9M1HPAdxLREvyVL0pKyNsJR2wpN7@mail.gmail.com \
    --to=antriksh.pany@gmail.com \
    --cc=apenwarr@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=mfwitten@gmail.com \
    /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).