All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.kabel.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Git versus Hg
Date: Wed, 12 Mar 2008 15:28:13 +0100	[thread overview]
Message-ID: <fr8p9u$8s0$1@ger.gmane.org> (raw)
In-Reply-To: <f96d234e0803120708r3286e264w6fbd21e6381bc235@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Cliff Brake schreef:

| Mercurial looks very interesting and nice in many aspects, but I have
| not used it yet.  It seems to me one of the fundamental differences is
| the concept of cheap/easy local branches.  Mercurial is working on
| something like that
| (http://www.selenic.com/mercurial/wiki/index.cgi/LocalBranches), but
| it is obviously not central to its philosophy like git .  The idea of
| creating many local branches a normal port of your development
| workflow seems unique to git.  As the gitmagic link below states, it
| makes it very easy to switch context to fix a bug, and then resume
| work on another feature.  This is a lot more than just "being good at
| generating patches"; it is a change in the way we work.

I can see how that's a good thing for what I call "traditional
application development" where a bunch of source files get compiled into
a single application (kernel, u-boot, xserver etc) where working on
multiple things at once doesn't work, since it makes building and
testing a nightmare. Easy branching solves that.

But OE isn't like that, it's a collection of build descriptions, which
makes it possible to be working on a 1000 different recipes at the same
time. This also is one of the reasons why mtn is so slow for us: lots of
files with a shortlived life spam and ±30 commits per day.

I like hg so much because it's the svn to monotones cvs: virtually
identical UI, without the crap.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFH1+h9MkyGM64RGpERAjc6AKCF0CIEIJml44MVR8xhuCxw4PwHIACfSnMh
rMWrhQTsv+0T6E6f7qWDT8U=
=lmbo
-----END PGP SIGNATURE-----




  reply	other threads:[~2008-03-12 14:30 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-11 23:53 Git versus Hg Philip Balister
2008-03-12  1:56 ` Khem Raj
2008-03-12  7:57 ` Esben Haabendal
2008-03-12  9:16 ` pHilipp Zabel
2008-03-12 13:32   ` Rodrigo Vivi
2008-03-12 14:51   ` Tom Cooksey
2008-03-12 15:22     ` Paul Sokolovsky
2008-03-12 15:35       ` Tom Cooksey
2008-03-12 14:08 ` Cliff Brake
2008-03-12 14:28   ` Koen Kooi [this message]
2008-03-13 14:33     ` Cliff Brake
2008-03-13  8:15   ` Paul Sokolovsky
2008-03-13 11:28     ` Richard Purdie
2008-03-13 19:00       ` Paul Sokolovsky
2008-03-13 20:45         ` Richard Purdie
2008-03-13 14:26     ` Cliff Brake
2008-03-13 15:29       ` Koen Kooi
2008-03-13 15:41       ` Koen Kooi
2008-03-13 20:03         ` Tom Rini
2008-03-13 19:20       ` Paul Sokolovsky
2008-03-13  8:58 ` Koen Kooi
2008-03-13  9:18   ` Paul Sokolovsky
2008-03-13  9:39   ` Esben Haabendal
2008-03-13 10:57   ` Richard Purdie
2008-03-13 11:27   ` pHilipp Zabel
2008-03-13 11:35     ` Marcin Juszkiewicz
2008-03-13 12:17     ` Richard Purdie
2008-03-14 19:44 ` Koen Kooi

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='fr8p9u$8s0$1@ger.gmane.org' \
    --to=koen@dominion.kabel.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.