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.comThere is no social pressure if no one is reading the list, because it's spammed by a bot.. I believe it's too many emails at the email rate the build system is currently sending. I'd vote to either send those mail somewhere else or to find a way to send a single email for all projects and only when a breakage starts (i.e. not for every commit) Please excuse typos. Written with a touchscreen keyboard. -- Regards, Alexander Chemeris CEO Fairwaves, Inc. https://fairwaves.co On Jan 18, 2017 10:15 AM, "Harald Welte" <laforge at gnumonks.org> wrote: > Dear all, > > On Tue, Jan 17, 2017 at 08:01:06PM +0000, OBS Notification wrote: > > Package network:osmocom:nightly/osmo-trx failed to build in > xUbuntu_16.04/x86_64 > > should we keep the build notifications here on this list (which probably > would mean more build failures right now than human discussion), or > should I send them to the redmine or other list? Even a new list? > > I am somewhat undecided. Having the posts here means that the social > pressure increases to fix those issues *fast*. However, if that's not > possible for some reason, we get continued mails...What do you think? > > Regards, > Harald > > -- > - 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) > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20170118/3ce72793/attachment.htm>