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/.
Harald Welte laforge at gnumonks.orgOn Thu, Mar 17, 2011 at 10:08:47PM +0100, Sylvain Munaut wrote: > Hi, > > > > 1) First, make a copy of libosmocore.git to libosmo-gsm.git. This is > > done to avoid losing the history in the new libosmo-gsm.git library. > > Can't this be made with git filter-branch somehow ? I think we might just build libosmo-gsm as part of the libosmocore.git repository, similar to what we do for libosmovty. But this may be a matter of personal taste ;) What do others think about it? I think splitting the include paths and the .so file names makes users (i.e. the application programs) aware that it is two libraries. Splitting the git repositories doesn'nt really buy us anything apart from yet another git checkout/update/configure/make/... that needs to be executed. If at some future point we want to split the repositories, it will not incur any changes to the application programs like openbsc, as they already check for two different pkgconfig etc. -- - Harald Welte <laforge at gnumonks.org> http://gnumonks.org/ ============================================================================ We all know Linux is great...it does infinite loops in 5 seconds. -- Linus