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/op25-dev@lists.osmocom.org/.
ikj1234i@yahoo.com [op25-dev] op25-dev at yahoogroups.comGreetings It looks like the balint256 'op25' repo tracks the op25 repo at op25.osmocom.org only up to commit 2051a96198c. The op25.osmocom.org repo has more than a dozen additional commits beyond that, which means that the balint256 op25 install is approx. one year out of date. All of balint's changes don't affect the op25_repeater, so there shouldn't be a big hassle when the time comes to merge everything into master. It looks only like one or two CMakeLists.txt files might have merge conflicts, YMMV. Accordingly, I recommend as follows (until such time as the merge may happen) - use only the op25.osmocom.org build when running scope.py - use only the balint256 one with balint's associated changes - keep them otherwise separate Max ps. Knuckle Punch to Balint!! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/op25-dev/attachments/20151128/579f029e/attachment.htm>