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

Mike Westerhof mwester at dls.net
Wed Mar 12 22:48:51 UTC 2008


 On Wed 12/03/08  5:32 PM , Paul Sokolovsky pmiscml at gmail.com sent:
> Hello,
> 
> On Wed, 12 Mar 2008 23:07:03 +0100
> "Leon Woestenberg" le
> on.woestenberg at gmail.com> wrote:
> > Hello Paul,
> > 
> > On Wed, Mar 12, 2008 at 10:40 PM, Paul Sokolovsky pmiscml at gma
> il.com>> wrote:
> > >  mirroring, but Monotone with its super-cool concept
> of unbelievably> >  cheap branches (so-called heads), make it just well
> robust - even> > if
> > >
> > Multiple heads and lightweight branches are two
> different things.
> Probably also because of different numbers of hexadecimal digits?
> 
> > 
> > A branch has a name/tag that tells me what is happening
> in that branch> or who is making it happen.
> 
> And heads have head revision and change logs too!
> 
> > 
> > In contrast, multiple heads does not help me in any way
> as a tool for> branching, nor can I easily track someone else's work
> in his "head".
> That's because you've stuck with that old and boring concept of
> "lightweight branches". People who grasped heads novelty enjoy it very
> much. Well, the same can be said about the people who didn't drop
> everything to endeavor into those "lightweight branches" - they enjoy
> classy branches with not the lesser passion than the other two groups.
> 
> 
> Well, but the talk was about mirroring and syncing potentially
> incompatible changes. Do lightweight branches help with this?
> 
> > 
> > Regards,
> > -- 
> > Leon
> 
> []
> 
> 
> -- 
> Best regards,
> Paul                          pmiscml at gma
> il.com

I think this has gotten to the point where the arguments is for the sake of arguing, and little else.  I'm surprised that it hasn't been mentioned that "hg" has the advantage that its name is only two characters, a 33% savings in overhead compared to most other scm tools we've discussed.


So, who makes this decision, and what's the timeframe?

Mike  (mwester)

Oh - btw, lightweight branching implies working, reliable tools to identify diffs and merge them, that's the part that really needs to be considered rather than how easy it is to just create a branch.






More information about the Openembedded-devel mailing list