git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Pulling one commit at a time.

From
Matthieu Moy <matthieu.moy@imag.fr>
Date
Aug 24, 2009, 11:07 UTC
Message-ID
<vpqskfhbhcz.fsf@bauges.imag.fr>
In-Reply-To
<4A92703E.90007@microchip.com>
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
Previous: Sanjiv GuptaNext: Avery Pennarun
Message 18 of 20 in “Pulling one commit at a time.”
  1. Sanjiv GuptaAug 23, 2009
  2. Alex RiesenAug 23, 2009
  3. Adam BrewsterAug 23, 2009
  4. Sam VilainAug 23, 2009
  5. Nanako ShiraishiAug 23, 2009
  6. Junio C HamanoAug 23, 2009
  7. Sanjiv GuptaAug 24, 2009
  8. Kai BlinAug 24, 2009
  9. Sanjiv GuptaAug 24, 2009
  10. Sean EstabrooksAug 24, 2009
  11. Erik Faye-LundAug 24, 2009
  12. Erik Faye-LundAug 24, 2009
  13. Matthieu MoyAug 24, 2009
  14. skillzero@gmail.comAug 24, 2009
  15. Matthieu MoyAug 24, 2009
  16. David AguilarAug 24, 2009
  17. Sanjiv GuptaAug 24, 2009
  18. Matthieu MoyAug 24, 2009
  19. Avery PennarunAug 24, 2009
  20. Sanjiv GuptaAug 24, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.