Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.kabel.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Git versus Hg
Date: Thu, 13 Mar 2008 16:41:32 +0100	[thread overview]
Message-ID: <frbhvc$gg8$1@ger.gmane.org> (raw)
In-Reply-To: <f96d234e0803130726q446bb89dg3698e2cec8c675e3@mail.gmail.com>

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

Cliff Brake schreef:

| I still maintain that that tools do impact developer workflow, and
| this should be a serious consideration when selecting tools.  What is
| the workflow that will maximize the productivity and output of the OE
| community?  The tool selection should follow.

Having been through the bk->mtn switchover and the re-evaluation I
noticed that people who said "I will start contributing (much more) to
OE if you weren't using bitkeeper" didn't actually start contributing
*at all*, so I'm extremely sceptical of the promised influx of a
gazillion ISVs, OEMs, ODMs and users with a switch to hg/git/vss.

All I can see is that the people taking care of the OE infrastructure
(Mickey and me) will have to allocate some weeks to do a good
changeover[1], and we both aren't known for our copious amounts of spare
time that would be needed.

regards,

Koen

[1] As it is, we were(are?) beginning the move of large parts of the
existing infrastructure to a new machine, but that's put on hold[2] due
to this discussion.
[2] Yes, that's why you haven't seen any commits mails lately.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFH2UsrMkyGM64RGpERAlvcAJ92SgGXGs8amaDIN1ef+JAlxXtqmgCgqTkF
4vrvx1JEyVXseQRAp7D2w1o=
=594a
-----END PGP SIGNATURE-----




  parent reply	other threads:[~2008-03-13 15:43 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
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 [this message]
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='frbhvc$gg8$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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox