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

Monotone workflow compared to Git workflow ( was RE: Git vs Monotone)

From
CCCraig L. Ching <cching@mqsoftware.com>
Date
Jul 31, 2008, 19:48 UTC
Message-ID
<63BEA5E623E09F4D92233FB12A9F79430238A5EE@emailmn.mqsoftware.com>
In-Reply-To
<alpine.LFD.1.10.0807311211260.3277@nehalem.linux-foundation.org>
> -----Original Message-----
> From: git-owner@vger.kernel.org 
> [mailto:git-owner@vger.kernel.org] On Behalf Of Linus Torvalds
> Sent: Thursday, July 31, 2008 2:18 PM
> single database for git, but wants to force a full clone for 
> each. Not to mention that in git, you'd normally not do 11 
> clones to begin with, you'd just do 11 branches in one repo.
>

I have a question about this. I asked this awhile back and didn't really get any satisfactory answers except to use git-new-workdir, which makes git behave a lot like monotone. In our workflow, we do create branches for nearly everything, but we do find that we have a need to keep the build artifacts of those branches isolated from each other because rebuilding is expensive. IOW, we have this sort of workflow:

git checkout A [work on A, build, test, do some commits] git checkout B [work on B, build, test, do some commits] git checkout A [work on A, re-build, test, do some commits]

We find ourselves constantly having to shift gears and work on other things in the middle of whatever it is we're currently working on. For instance, in the scenario above, A might be branch that contains a feature going into our next release. B might be a bugfix and takes priority over A, so you have to leave A as-is and start work on B. When I come back to work on A, I have to rebuild A to continue working, and that's just too expensive for us. So we use the monotone-like new-workdir which allows us to save those build artifacts.

So, that said, I ask again, am I missing something? Is there a better way to do this? How do the kernel developers do this, surely they're switching branches back and forth having to build in-between?

Show 6 quoted lines
> 			Linus
> --
> To unsubscribe from this list: send the line "unsubscribe 
> git" in the body of a message to majordomo@vger.kernel.org 
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Cheers, Craig

Previous: David KastrupNext: Linus Torvalds
Message 17 of 33 in “Git vs Monotone”
  1. Sverre RabbelierJul 31, 2008
  2. Stephen R. van den BergJul 31, 2008
  3. Petr BaudisJul 31, 2008
  4. Jeff KingJul 31, 2008
  5. Craig L. ChingJul 31, 2008
  6. Sverre RabbelierJul 31, 2008
  7. Jeff KingJul 31, 2008
  8. Linus TorvaldsJul 31, 2008
  9. Craig L. ChingJul 31, 2008
  10. Linus TorvaldsJul 31, 2008
  11. Junio C HamanoJul 31, 2008
  12. Linus TorvaldsJul 31, 2008
  13. Felipe ContrerasAug 23, 2008
  14. Blum, RobertJul 31, 2008
  15. Robin RosenbergAug 10, 2008
  16. David KastrupAug 1, 2008
  17. Monotone workflow compared to Git workflow ( was RE: Git vs Monotone)Craig L. Ching, Jul 31, 2008
  18. Linus TorvaldsJul 31, 2008
  19. Shawn O. PearceJul 31, 2008
  20. Craig L. ChingJul 31, 2008
  21. Björn SteinbrinkJul 31, 2008
  22. Avery PennarunJul 31, 2008
  23. Linus TorvaldsJul 31, 2008
  24. Martin LanghoffJul 31, 2008
  25. Linus TorvaldsJul 31, 2008
  26. Dmitry TorokhovAug 1, 2008
  27. Linus TorvaldsAug 1, 2008
  28. Linus TorvaldsAug 1, 2008
  29. Sean EstabrooksJul 31, 2008
  30. Theodore TsoJul 31, 2008
  31. Theodore TsoJul 31, 2008
  32. Sverre RabbelierAug 1, 2008
  33. Daniel BarkalowAug 1, 2008

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.