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

Re: Git vs Monotone

From
Theodore Tso <tytso@mit.edu>
Date
Jul 31, 2008, 19:24 UTC
Message-ID
<20080731192405.GC20819@mit.edu>
In-Reply-To
<bd6139dc0807311113n50dda9f0t1aab46b724510de2@mail.gmail.com>
On Thu, Jul 31, 2008 at 08:13:59PM +0200, Sverre Rabbelier wrote:
> 
> I just read this blog post [0] in which one of the Pidgin devs sheds
> his light on their 'tool choice'. In the post he mentions the
> following figures:

The main thing this proves was that the Pidgin devs were most familiar with Monotone, and weren't sufficiently familiar with git; hence, they didn't know how to do a fair comparison. First of all, sure, if they are willing to use a single working directory and want to switch between branches using "git checkout", that works well. But suppose they really want separate working directories. The simplist and easist way is to use "git clone -s".

So if they do:

git clone git://github.com/felipec/pidgin-clone.git pidgin git clone -s pidgin clone-1 git clone -s pidgin clone-2 git clone -s pidgin clone-3 git clone -s pidgin clone-4 git clone -s pidgin clone-5 git clone -s pidgin clone-6 git clone -s pidgin clone-7 git clone -s pidgin clone-8 git clone -s pidgin clone-9 git clone -s pidgin clone-10

The net disk usage is 746 megabytes, as compared to the 900 megabytes claimed in the blog post. The main difference is the git database is only takes 87 megabytes, compared to the 229 megabytes for the Monotone database. The main issue is the pidgin developers simply didn't know how to use the -s flag so they didn't need to duplicate the git database for every single clone.

Shrug; whatever, I've always said the biggest issue for any tool is what the developers are familiar with. It may be that monotone was the right choice for the pidgin core developers, if they weren't familiar enough with git.

						- Ted
Previous: Theodore TsoNext: Sverre Rabbelier
Message 31 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.