qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: "M. Warner Losh" <imp@bsdimp.com>
Cc: mle+tools@mega-nerd.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Switch to GIT. Why?
Date: Mon, 27 Apr 2009 10:22:37 -0400	[thread overview]
Message-ID: <20090427142237.GV3795@csclub.uwaterloo.ca> (raw)
In-Reply-To: <20090427.075432.756921142.imp@bsdimp.com>

On Mon, Apr 27, 2009 at 07:54:32AM -0600, M. Warner Losh wrote:
> Yes.  And that's why you can only check out entire trees, and never
> subtrees, with git and hg, but you can with svn.  git and hg force a
> small view of the system to be its own repo.  So something the size of
> X11 or FreeBSD could never use git or hg without breaking the
> integrated tree model.  FreeBSD used svn to not break it because we
> like the development model we have (and think Linus' talk at google
> was very arrogant to suggest it was broken), while the X11 folks broke
> their tree up into lots of modules, and got out of the making sure it
> all worked together business (which makes integrating X11 into systems
> harder now, alas).

It is certainly a tradeoff.  Of course with svn, when you do a checkout,
you get one version of the code.  If you want to search te history,
you have to talk to the server.  With git a "checkout" (clone) gets you
everything, history and all.  Makes searches and switching revisions
much faster, but makes the initial copy take much longer.

What X11 did also made it much easier to fix bugs, since you can now
work on the smaller pieces and release them much easier than you can
release the whole thing.  As for making sure it all works together,
I am not convinced it made it harder.  Seems development and such has
gotten much faster and better as a result.  It is no longer completely
overwhelming to work with.

> For qemu, none of these issues are likely to be an issue, but it is
> something to keep in mind...

True.  Of course as long as you have one tree per application, even
freebsd should be able to work with something like git.  Having one
giant tree for everything sounds nuts to me.  No idea how they do it
(I can't stand the userland of BSD in general, so I don't work with it.
Good applications, good kernel, lousy setup. :)  Debian kfreebsd may
change that of course.)

-- 
Len Sorensen

  reply	other threads:[~2009-04-27 14:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <A1B59730-636E-43B7-88AE-9C7057D41F17@hotmail.com>
2009-04-26  5:28 ` [Qemu-devel] Switch to GIT. Why? C.W. Betts
2009-04-26  5:52   ` Erik de Castro Lopo
2009-04-26  7:13     ` M. Warner Losh
2009-04-26  8:15       ` Ralf Baechle
2009-04-27 13:10       ` Lennart Sorensen
2009-04-27 13:54         ` M. Warner Losh
2009-04-27 14:22           ` Lennart Sorensen [this message]
2009-04-27 14:42             ` M. Warner Losh
2009-04-26  7:20   ` Andreas Färber

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=20090427142237.GV3795@csclub.uwaterloo.ca \
    --to=lsorense@csclub.uwaterloo.ca \
    --cc=imp@bsdimp.com \
    --cc=mle+tools@mega-nerd.com \
    --cc=qemu-devel@nongnu.org \
    /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).