Re: Git versus Hg

[Tom Cooksey <thomas.cooksey@trolltech.com>]

> What is still unclear to me is how well a shared git repository with
> push access for multiple parties is going to work. The mobile-linux
> repository on serenity had some kind of permission trouble before we
> added the group permission fixup in the post-update hook.

In Trolltech, we are currently "migrating" from perforce to git. At the
moment my work-flow is to use git-p4 script to pull in changes from
the central p4 repo. Then I use git locally with several different 
branches (one for each area I'm working on). When I'm happy with
something and want to push it into our main repo, I again use the
git-p4 script.

This kindof hybrid style of working suits me pretty well as I know I
can't mess anything up in the central repo with just git. :-) The git-p4
script integrates the change history etc. so it's like working nativly
with git. 

I've also tried to push things with git and found it's pretty tough to 
get right the first time you try.

I've noticed there are similar integration scripts for svn. Perhaps 
there could be a "central" svn repo, then individual developers can use 
git locally. You can still setup git remotes to cherry pick other people's 
commits, if you need that.


As an OpenEmbedded newbie, one more thing I would say is this:

The learning curve for OpenEmbedded is huge. The documentation
is rather sparce and I personally found trying to understand what's
going on very difficult (I'm also a python newbie which probably 
didn't help!). If you choose a well-known SCM system, it's one less 
thing new potential developers need to learn. They have enough to 
learn as it is.



Cheers,

Tom

PS: Personally, I'd never heard of Hg until reading threads on this list.