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 "Lev Walkin's asn1 compiler". The branch, aper-prefix has been updated discards 22eb61bbe9d7be959d03741e413a16f95f846610 (commit) discards 1d73b9b26876c7a365871bbcb6cf323f0e84ed98 (commit) via 98427f733c59baba8d6aa4daea3dc53d315458a1 (commit) via aa37b8cf4d8b6f454974e070b207d80cb6711af0 (commit) via 539d484434be91eeab55e0eff3ce63cfe3a2453a (commit) via 50823b81391418465f378a73aa4a3e92af6d0f27 (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 (22eb61bbe9d7be959d03741e413a16f95f846610) \ N -- N -- N (98427f733c59baba8d6aa4daea3dc53d315458a1) 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/asn1c/commit/?id=98427f733c59baba8d6aa4daea3dc53d315... commit 98427f733c59baba8d6aa4daea3dc53d315458a1 Author: Holger Hans Peter Freyther <holger@moiji-mobile.com> Date: Wed Jan 13 13:49:52 2016 +0100 automake: automake 1.11.1 does not have this macro, ignore it then http://cgit.osmocom.org/asn1c/commit/?id=aa37b8cf4d8b6f454974e070b207d80cb67... commit aa37b8cf4d8b6f454974e070b207d80cb6711af0 Author: Harald Welte <laforge@gnumonks.org> Date: Thu Sep 10 09:31:18 2015 +0200 prefixing of generated types using a ASN1C_PREFIX environment variable When generating code for multiple ASN.1 syntaxes that have clashing names, we need to add a prefix in order to prevent clashes in the global C symbol namespace. Using the ASN1C_PREFIX environment variable and this patch serves as a work-around to that. All non-basic type names as well as references to that type and source code + header file names will be pre-fixed accordingly. http://cgit.osmocom.org/asn1c/commit/?id=539d484434be91eeab55e0eff3ce63cfe3a... commit 539d484434be91eeab55e0eff3ce63cfe3a2453a Author: roux <roux@mycompany.com> Date: Sat Apr 30 16:03:12 2016 +0200 Fix a bug in asn1c PER code when skipping unknown extension Basically when skiping an unknown extension, asn1c did read 24 bits per 24 bits and later on failed if the remaining bits (up to 23) were superior to 8. The patch reads 1 bit per 1 bit. (imported from openairinterface5g/openair2/RRC/LITE/MESSAGES/asn1c/asn1cpatch.p0) http://cgit.osmocom.org/asn1c/commit/?id=50823b81391418465f378a73aa4a3e92af6... commit 50823b81391418465f378a73aa4a3e92af6d0f27 Author: Harald Welte <laforge@gnumonks.org> Date: Sat Apr 30 17:31:33 2016 +0200 fix APER encoding of integer (backport from openairinterface) The number of bytes used by an APER encoded integer depends on its actually encoded value, not on the maximum value that could be possibly encoded. The old code would e.g. always use 24 bits if the maximum encoded value would require 24 bits. To give an example RANAP MaxBitrate (INTEER 1 .. 16000000) value 64000 was previously encoded as "80 00 f9 ff", while it is now the correct representation "40 f9 ff". Thanks to Dieter Spaar for detecting this problem in the Osmo-IUH generated RANAP output, and thanks to openairinterface for fixing the bug in their code (sadly not contributed to upstream asn1c, though). ----------------------------------------------------------------------- Summary of changes: skeletons/INTEGER.c | 27 ++++++++++++++++++++++----- skeletons/per_opentype.c | 2 +- 2 files changed, 23 insertions(+), 6 deletions(-) hooks/post-receive -- Lev Walkin's asn1 compiler