From: Koen Kooi <koen@dominion.kabel.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Git versus Hg
Date: Fri, 14 Mar 2008 20:44:04 +0100 [thread overview]
Message-ID: <freki4$mko$1@ger.gmane.org> (raw)
In-Reply-To: <47D71B8F.1030108@balister.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Philip Balister schreef:
| Given the only serious contenders for possible SCM's for OE appear to be
| git or Hg, I am curious about the expertise level available on this list.
|
| Basically, let us know if you use git or Hg on a regular basis in a two
| way workflow and consider yourself knowledgeable on sorting out problems
| that crop up.
Hg can support git style local branches:
http://www.selenic.com/mercurial/wiki/index.cgi/LocalbranchExtension
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFH2tWEMkyGM64RGpERAgJaAJ9Y4DyCcyDvKVBYVkVWS8RGFoIFLQCgh2nB
/ZNlKbbs2r+hkpctgQSnR5I=
=9cPZ
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2008-03-14 19:46 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
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 [this message]
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='freki4$mko$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.