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/osmocom-commitlog@lists.osmocom.org/.
gitosis at osmocom.org gitosis at osmocom.orgThis is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Osmocom BTS-side code (Abis, scheduling, ...)".
The branch, master has been updated
discards 8b4700dc967bd751a46b42b5789df9bd5ff0335c (commit)
discards 73b071b1d24f814979adcc772480ccd4abb878d1 (commit)
via 61f9158eaffd7f4be76f7a44d803d9ba14988d92 (commit)
via 1ba0cfe9c0fe8423f9d2f8676ad39c5fd53e237f (commit)
This update added new revisions after undoing existing revisions. That is
to say, the old revision is not a strict subset of the new revision. This
situation occurs when you --force push a change and generate a repository
containing something like this:
* -- * -- B -- O -- O -- O (8b4700dc967bd751a46b42b5789df9bd5ff0335c)
\
N -- N -- N (61f9158eaffd7f4be76f7a44d803d9ba14988d92)
When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
http://cgit.osmocom.org/osmo-bts/commit/?id=61f9158eaffd7f4be76f7a44d803d9ba14988d92
commit 61f9158eaffd7f4be76f7a44d803d9ba14988d92
Author: Neels Hofmeyr <nhofmeyr at sysmocom.de>
Date: Fri Jun 23 23:32:37 2017 +0200
Revert "RSL: receive and send multiple SI2q messages"
This reverts commit 340cff51f49f6e798cb5fb6d1b9febdd09902906.
osmo-gsm-tester detected a regression due to this commit, when running
osmo-bts-trx. The modems timed out when waiting for them to register with the
osmo-bts-trx network. osmo-bts-sysmo is apparently not affected. No further
details on the failure cause are known yet. The failure is shown for example by
http://jenkins.osmocom.org/jenkins/view/osmo-gsm-tester/job/osmo-gsm-tester_run/868/
Change-Id: I15bca30ddc09a7a3044096626016f6130d07636c
http://cgit.osmocom.org/osmo-bts/commit/?id=1ba0cfe9c0fe8423f9d2f8676ad39c5fd53e237f
commit 1ba0cfe9c0fe8423f9d2f8676ad39c5fd53e237f
Author: Neels Hofmeyr <nhofmeyr at sysmocom.de>
Date: Fri Jun 23 23:32:32 2017 +0200
Revert "RSL: check for abnormal SI2q values"
This reverts commit 186c6bac0758b6f94aa101e151664b0dea5d8975.
osmo-gsm-tester detected a regression due to commit
340cff51f49f6e798cb5fb6d1b9febdd09902906, which above commit apparently depends
on. Revert this along to avoid conflicts.
Change-Id: I456e9add788393ca781213cef31b5bc3d48fd531
-----------------------------------------------------------------------
Summary of changes:
hooks/post-receive
--
Osmocom BTS-side code (Abis, scheduling, ...)