osmo-iuh.git branch osmocom/gerrit-test updated. 216225cde8a6c08b68a718326a9b83b1a8095d7d

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.org
Mon Jul 11 15:55:06 UTC 2016


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 code for Iuh interface".

The branch, osmocom/gerrit-test has been updated
  discards  866840f0708689c9c1388d113ae31430c31cf8cf (commit)
       via  216225cde8a6c08b68a718326a9b83b1a8095d7d (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 (866840f0708689c9c1388d113ae31430c31cf8cf)
            \
             N -- N -- N (216225cde8a6c08b68a718326a9b83b1a8095d7d)

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-iuh/commit/?id=216225cde8a6c08b68a718326a9b83b1a8095d7d

commit 216225cde8a6c08b68a718326a9b83b1a8095d7d
Author: Neels Hofmeyr <neels at hofmeyr.de>
Date:   Mon Jul 11 17:10:49 2016 +0200

    jenkins.sh: fix, remove code dup
    
    Have a bash function to build each dependency with the same commands.  There is
    a tradeoff: having each dependency build with the same function means you can't
    easily tweak one of the dependencies. OTOH having a unified function means a)
    more readable script, b) that we're sure not to forget some steps and c) no
    need to do the same edit n times.
    
    Set the PKG_CONFIG_PATH globally. Also a tradeoff: if a future addition
    wouldn't need the same PKG_CONFIG_PATH, this would make things ugly. But that
    is actually quite unlikely, and the readability improvement is substantial.
    
    Use env variables to remember local paths. That means we always are sure to cd
    to the same absolute base path, which a 'cd ..' can't guarantee; also, we avoid
    possible typos for e.g. "$deps/install".
    
    Build sysmocom/sctp branch of libosmo-netif, as needed for libosmo-sccp's
    sysmocom/iu branch.
    
    'make regen' first, to generate the .c from asn1, needed by the build.
    
    Change-Id: Ia7b4b9788b9c951f8be00cc5ae72a9c0a776fe64

-----------------------------------------------------------------------

Summary of changes:
 contrib/jenkins.sh | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)


hooks/post-receive
-- 
Osmocom code for Iuh interface



More information about the osmocom-commitlog mailing list