On Sat, Jun 16, 2012 at 11:33:54AM +0400, Alexander Chemeris wrote:
> Hi Harald,
Hi,
>
> Could we setup a commit mailing list to know when someone commits?
>
> And is an ability to make commit reviews, like in Google Code or github?
so far the amount of external patches were always so low that reviewing
them on the mailinglist were okay. I would propose we do the same for the
PCU. In case this doesn't scale we can introduce a Gerrit.
does it make sense?
holger
--
- Holger Freyther <hfreyther(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Schivelbeiner Str. 5
* 10439 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Directors: Holger Freyther, Harald Welte
Hi Alexander,
On Sat, Jun 16, 2012 at 11:33:54AM +0400, Alexander Chemeris wrote:
> Could we setup a commit mailing list to know when someone commits?
We have normally all projects' commitlog at
http://lists.osmocom.org/mailman/listinfo/osmocom-commitlog
and I have just now added osmo-pcu.git to this list
> And is an ability to make commit reviews, like in Google Code or github?
I use neither of them, and thus don't really know what you are referring
to.
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Hi Alexander, Ivan and everyone else,
as per our previous private discussions, I've now imported the PCU code
to the repository, which you can see at
http://cgit.osmocom.org/cgit/osmo-pcu/
The history of the old repository was imported using git filter-branch.
I've also added an auto-foo skeleton and cleaned up some bits.
As libosmo-gb is still not properly separated from openbsc.git, the
required tree layout is something like:
ancestor/openbsc
ancestor/osmo-pcu
Right now the code doesn't build yet. Some of it is remaining OpenBTS
dependencies, some of it is the fact that the code apparently never
compiled on 64bit systems:
> csn1.cpp:65:69: error: invalid initialization of reference of type 'unsigned int&' from expression of type 'size_t {aka long unsigned int}'
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)