[oe] Reconsidering the work flow and how the SCM system fits in

Koen Kooi koen at dominion.kabel.utwente.nl
Wed Mar 12 20:45:18 UTC 2008


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

Leon Woestenberg schreef:
| Hello Koen, all,
|
| On Wed, Mar 12, 2008 at 8:00 PM, Koen Kooi
| <koen at dominion.kabel.utwente.nl> wrote:
|> -----BEGIN PGP SIGNED MESSAGE-----
|>  | http://lists.freedesktop.org/archives/cairo/2006-February/006255.html
|>  |
|>  | His arguments on the (main two) differences strongly favors me to move
|>  | to GIT, not HG.
|>
|>  Actually it shows that hg fits better into the OE way of using a DSCM:
|>  central repo (and mirrors) with distributed developers.
|>
| Quoting Carl: "Namely, it [hg] appears to force a more centralized,
| (or at least, a more strictly hierarchical), model on the development
| process, while git allows a more fully distributed model making it
| easier for users to pull (even speculatively with "fetch") from
| multiple sources, track them in the local repository as separate
| branches and merge when appropriate."
|
| Carl carefully uses the words "force" and "allows". Git does not
| preclude a central model, whilst still allowing more centralized
| development.
|
| And the centralized way we work currently is also DUE to us using mtn,
| i.e. it forces us more or less to work this way.

That isn't true, after the bitkeeper switch we *decided* to to it this
way, instead of going fully distributed.


| Some thoughts:
| - Why wouldn't the kernel model work for us? There is one upstream
| tree and distributed developers.
| - Suppose we were using GIT today, would we consider going to HG or MTN?

Yes, since we would all remember git 1.4 throwing away all our local
changes, the lack of docs and the horrible, horrible ui.

| - Suppose we were using HG today, would we consider going to GIT or MTN?

I don't think we would since we would go for horrible UI or slowness.

| Proposal: Can we work with MTN and GIT, or MTN and HG in parallel?

We did that before and did go for hg because of a bug in 'hg serve',
which has been solved nowadays.
And if we go for hg there is no learning curve, since the hg ui was
based on the monotone one.


regards,

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

iD8DBQFH2EDeMkyGM64RGpERAm3MAKCBouBagUxRyN9NXK4Ww5PB1dFu0ACbB9ge
TpsBfnHFA8/D6YVp4Eu3WtI=
=XwPg
-----END PGP SIGNATURE-----





More information about the Openembedded-devel mailing list