From: Matthieu Moy <Matthieu.Moy@imag.fr>
To: Sanjiv Gupta <sanjiv.gupta@microchip.com>
Cc: David Aguilar <davvid@gmail.com>,
Nanako Shiraishi <nanako3@lavabit.com>,
git@vger.kernel.org
Subject: Re: Pulling one commit at a time.
Date: Mon, 24 Aug 2009 13:07:08 +0200 [thread overview]
Message-ID: <vpqskfhbhcz.fsf@bauges.imag.fr> (raw)
In-Reply-To: <4A92703E.90007@microchip.com> (Sanjiv Gupta's message of "Mon\, 24 Aug 2009 16\:19\:34 +0530")
Sanjiv Gupta <sanjiv.gupta@microchip.com> writes:
> I was looking for post-mortem change-that-introduced-bug.
If so, then you don't need to test every commit. As David mentionned,
"git bisect" is your friend, and will do a binary search, finding the
culprit commit much more efficiently (run the testsuite log(n) times
instead of n times).
OTOH, if you want some kind of quality insurance (i.e. check that
every commit is OK, including the case where a commit introduces a
bug, and the next one fixes it), bisect is rather helpless.
--
Matthieu
next prev parent reply other threads:[~2009-08-24 11:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <F536B7C316F9474E9F7091239725AC9A02FA7F44@CHN-CL-MAIL01.mchp-main.com>
2009-08-23 16:48 ` Pulling one commit at a time Sanjiv Gupta
2009-08-23 20:11 ` Alex Riesen
2009-08-23 20:17 ` Adam Brewster
2009-08-23 20:19 ` Sam Vilain
2009-08-23 21:07 ` Nanako Shiraishi
2009-08-23 22:33 ` Junio C Hamano
2009-08-24 6:22 ` Sanjiv Gupta
2009-08-24 7:46 ` Kai Blin
2009-08-24 7:55 ` Sanjiv Gupta
2009-08-24 8:20 ` Sean Estabrooks
2009-08-24 8:20 ` Erik Faye-Lund
2009-08-24 8:22 ` Erik Faye-Lund
2009-08-24 8:28 ` Matthieu Moy
2009-08-24 8:33 ` skillzero
2009-08-24 8:41 ` Matthieu Moy
2009-08-24 10:22 ` David Aguilar
2009-08-24 10:49 ` Sanjiv Gupta
2009-08-24 11:07 ` Matthieu Moy [this message]
2009-08-24 18:19 ` Avery Pennarun
2009-08-24 19:08 ` Sanjiv Gupta
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=vpqskfhbhcz.fsf@bauges.imag.fr \
--to=matthieu.moy@imag.fr \
--cc=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=nanako3@lavabit.com \
--cc=sanjiv.gupta@microchip.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).