Re: monotone/git (was hello...)

[Michael Krelin <hacker@klever.net>]

> Well luckily I am not an ignorant git-fanboy :) Could you shortly point
> out to me the reasons why you think monotone is favorable over git for
> use with openembedded ? I will admit right away that my limitation with
> SCMs in large projects is more than limited. So i can only speak of
> my user experience with git vs my experience with monotone and i prefer
> the first.

Well, 1st - OE folks are used to monotone now. That's primary reason.
The second primary reason is that I know of some developers who seem to
dislike git. And if we're talking about technical reason, one I can
think of is that there's no non-ssh transport allowing push, which
complicates administration of our "central" repository. Basically,
monotone is not really used as a DSCM in OE, it's just a somewhat
centralized SCM which allows merges as well as forks.

Personally, I think the lack of tools like gitk makes mtn history almost
opaque which gets even more opaque and unreadable due to the lack of
features like rebase.

I do think also that potential corporate users of OE would appreciate
git (the mirror would mostly solve this, though) as *I* think it's much
easier with git to maintain own branch while picking the important
changes from our tree (contributing back will be more complicated, though).

The above is my personal opinion and I have to admit I may miss
something about monotone, since, although I've had no problems using it
both ways, I wouldn't say I'm a monotonic guru.

Love,
H