proliferation of repositories + branches (Re: osmo-combo build script)

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Alexander Chemeris alexander.chemeris at gmail.com
Thu Apr 28 20:31:12 UTC 2016


Hi Harald,

On Thu, Apr 28, 2016 at 3:57 PM, Harald Welte <laforge at gnumonks.org> wrote:
> On Thu, Apr 28, 2016 at 01:43:54PM +0200, Neels Hofmeyr wrote:
>> ...and I see that libosmocore and openbsc are in fact included from the
>> fairwaves github repositories.
>
> fairwaves have full commit access to the respective projects on
> git.osmocom.org, so I don't really think it is wise to further
> proliferate different repositories.

I was actually going to write that the only reason for this is
historical. Sergey didn't have commit access originally and was doing
development in our github clone. Now that he has commit access and
branches are pushed to git.osmocom.org, there is no real reason to
point to our github. I've updated the .gitmodules to point to
git.osmocom.org.

> The work should be focussed on merging and unifying the codebase, rather
> than further forking and confusing every single user and developer.
>
> We need one version of the code that works for everyone, particularly
> for core components like the libraries.

I'm totally with you on this.

-- 
Regards,
Alexander Chemeris.
CEO, Fairwaves, Inc.
https://fairwaves.co



More information about the OpenBSC mailing list