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

Re: Pulling one commit at a time.

From
David Aguilar <davvid@gmail.com>
Date
Aug 24, 2009, 10:22 UTC
Message-ID
<20090824102242.GA70861@gmail.com>
In-Reply-To
<4A92318F.6050105@microchip.com>
On Mon, Aug 24, 2009 at 11:52:07AM +0530, Sanjiv Gupta wrote:
> Excellent description. Thanks for that. I want to merge commits one by  
> one because I want to run a regression suite on each commit and  
> therefore know if any one is causing failures.
'git bisect' is your friend.

If your developers are disciplined and test each change as they commit it then you're going to have fewer problems.

If they aren't, then make 'em send you patches. Then you can at least 'git am' each one and run the tests at each step, including the critical steps where you merge various topics together.

I'm not sure what exactly you're trying to accomplish, though. I'm just making guesses without you telling us more.

Are you trying to do post-mortem change-that-introduced-bug finding (git bisect), commit-time bug prevention (patch-based workflows, using git commit hooks to disallow commits that fail the tests, etc), or is it something completely different?

HTH,
-- 
		David
Previous: Matthieu MoyNext: Sanjiv Gupta
Message 16 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.