From: git repository hosting Precedence: list To: osmocom-commitlog@lists.osmocom.org Date: Thu, 20 Dec 2012 19:20:07 +0100 Message-ID: Subject: osmo-bts.git branch zecke/openbsc-incdir updated. 0.1.0-20-g56698b8 Message: 7 This 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, zecke/openbsc-incdir has been updated discards ba02baa790832f2e1444f9e525a71500ae548ac0 (commit) discards 6628a8b0626e75d69b07ff8b879090e3035f799f (commit) discards f2ff93de9e4f94edcb4a05a25985077150e0e25f (commit) discards 03d69d8ddb64de74aa900cc2a78ba02b219bfa33 (commit) discards b1ff4b4d4e866c7a86bd0f2476d8156dd3e11a88 (commit) discards 23233f74f3998f4ca3d3c8da88740eddda7e45b8 (commit) discards cf49ee494e41467e8e6b7a95960cd4489fb5c4d6 (commit) discards 1ac11f06e295c1f7e0eb0c9fd6d001f15f547dde (commit) discards 1c33f189109c9f87003ce448bda29ce10ed7a2a2 (commit) discards facad31fdf8fc14f82e9df9db296ca5e48972615 (commit) discards 1bcfa4b8a426c51160ed70b2016afb622257cf11 (commit) via 56698b84e0e0caa373c74df8e76b5f476aee1d9a (commit) via db51f0d73efda28d4b83703d512cd7137beae9d8 (commit) via bcae2abff8dfeaab75b1bbe58c7659285a721822 (commit) via d1ffab96ca64111652fd850982ca00514b5b3531 (commit) via 61a1f996801cf682a4f4c508dea2b83aa6d4ddbf (commit) via 4fd0a84cf8959e84ae306510c25178f88acd2b88 (commit) via 9bd5afa0146285e596f0c1172a6a4920a1c8597a (commit) via 8d8ff80890ef6538b0340311b1bb3fc58e9c7e8d (commit) via 6f93861cfc161a0b3c5780ca61e4fe8fcdadb611 (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 (ba02baa790832f2e1444f9e525a71500ae548ac0) \ N -- N -- N (56698b84e0e0caa373c74df8e76b5f476aee1d9a) 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/cgit/osmo-bts/commit/?id=56698b84e0e0caa373c74df8e76b5f476aee1d9a commit 56698b84e0e0caa373c74df8e76b5f476aee1d9a Author: Holger Hans Peter Freyther Date: Thu Dec 20 00:21:38 2012 +0100 openbsc: Check for the presence of the gsm_data_shared.h header file http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=db51f0d73efda28d4b83703d512cd7137beae9d8 commit db51f0d73efda28d4b83703d512cd7137beae9d8 Author: Holger Hans Peter Freyther Date: Thu Dec 20 00:04:20 2012 +0100 openbsc: Introduce autoconf support to set the OpenBSC include directory Add autoconf support to set the path to the OpenBSC include directory so that openbsc/gsm_data_shared.h can be found there. http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=bcae2abff8dfeaab75b1bbe58c7659285a721822 commit bcae2abff8dfeaab75b1bbe58c7659285a721822 Author: Holger Hans Peter Freyther Date: Wed Dec 19 23:53:34 2012 +0100 openbsc: Prepare to allow to have the OpenBSC directory somewhere else Right now osmo-bts requires access to one OpenBSC header file and this requires that openbsc and osmo-bts git are in the same directory. Begin with making the location of the OpenBSC sourcecode configurable. This approach will allow to build osmo-bts on our Jenkins installation but now has the risk of more code including the openbsc/*.h header files. ----------------------------------------------------------------------- Summary of changes: configure.ac | 2 +- src/osmo-bts-sysmo/calib_file.c | 8 ++------ src/osmo-bts-sysmo/l1_if.c | 4 ++-- 3 files changed, 5 insertions(+), 9 deletions(-) hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)