[Olsr-dev] -lc fork

[Erik Tromp]

> > > Just a question, is there a reason why you created a new sourceforge
> > project instead of posting a
> > > patch to a recent olsrd version ?
> > 
> > I would like to, but then I have a few questions also:
> > 
> > 1. Can just anyone post/submit source code changes into the Mercurial 
> > repository?
> 
> Mercurial (or "hg" for short) as such is a distributed SCM (unlike CVS and
similar to
> git, arch, ...) without a technically defined (or
> necessary) central/primary/main repository.
> So basically one defines organizationally what the "official repository"
> is. Everyone may clone it (and implicitly base your copy on the original
as you will
> want to incorporate changes from the "official" one) and work similar to
CVS. But you
> can also publish your changed/edited hg tree (under whatever URL you have
access to).
> And other people can pull in changesets ("commits" IIRC in hg speak) from
your
> published hg tree(s).
> Hannes (who actually is the resident hg guru), please correct any faults!
> 
> As for the terminology: I purposely didn't use the word "fork" above as I
don't
> consider cloned trees a "fork" as long as one can pull commits in without
> any major effort.
> 
> I hope that answers question 2) and 3) somewhat too.



Well.... nearly.

I'm still curious who determines the contents of new releases. And by which
criteria,
and if there is some kind of (regression) test suite.

Thanks anyway for your short tutorial on hg. It's time for me to spend some
reading
into this source control system :-)

Erik