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.orgHi Neels,
On Sun, Dec 11, 2016 at 02:02:33AM +0100, Neels Hofmeyr wrote:
> The libosmocore commit aa00f99be2e4cc64ede20d8c9548b83054696581 adds a VTY item
> that's missing a doc string, hence breaking the openbsc build (which actually
> checks the doc strings unlike the libosmocore build job).
Sorry for that. And thanks for the clean-up.
> Anyway, so far I think it is sufficient to catch these hopefully few cases once
> the regular master build on jenkins.osmocore.org goes up red, like now.
yes, still it's sad. I am wondering what else we could do. Maybe
include an executable / test case that can verify the documentation
strings inside libosmocore itself?
I think specifically regarding vty documentation strings, this is not
the first time we have seen this problem.
--
- Harald Welte <laforge at gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)