falconia has uploaded this change for review. ( 
https://gerrit.osmocom.org/c/libosmo-netif/+/39278?usp=email )


Change subject: include/osmocom/netif/Makefile.am cosmetic: make it easier to 
extend
......................................................................

include/osmocom/netif/Makefile.am cosmetic: make it easier to extend

To make it easier to add new headers to osmonetif_HEADERS list,
make two cosmetic changes to it:

* List all currently exported headers in alphabetical order;
* Use $(NULL) construct so that every header-naming line ends
  with a backslash.

Change-Id: I05ecbdb44286b842e158278fb07479846cd66806
---
M include/osmocom/netif/Makefile.am
1 file changed, 4 insertions(+), 3 deletions(-)



  git pull ssh://gerrit.osmocom.org:29418/libosmo-netif refs/changes/78/39278/1

diff --git a/include/osmocom/netif/Makefile.am 
b/include/osmocom/netif/Makefile.am
index 3d8a56b..d518edb 100644
--- a/include/osmocom/netif/Makefile.am
+++ b/include/osmocom/netif/Makefile.am
@@ -4,14 +4,15 @@

 osmonetif_HEADERS = amr.h              \
                    datagram.h          \
-                   jibuf.h             \
-                   osmux.h             \
                    ipa.h               \
                    ipa_unit.h          \
+                   jibuf.h             \
+                   osmux.h             \
                    prim.h              \
                    rs232.h             \
                    rtp.h               \
-                   stream.h
+                   stream.h            \
+                   $(NULL)

 if ENABLE_LIBSCTP
 osmonetif_HEADERS += sctp.h

--
To view, visit https://gerrit.osmocom.org/c/libosmo-netif/+/39278?usp=email
To unsubscribe, or for help writing mail filters, visit 
https://gerrit.osmocom.org/settings?usp=email

Gerrit-MessageType: newchange
Gerrit-Project: libosmo-netif
Gerrit-Branch: master
Gerrit-Change-Id: I05ecbdb44286b842e158278fb07479846cd66806
Gerrit-Change-Number: 39278
Gerrit-PatchSet: 1
Gerrit-Owner: falconia <[email protected]>

Reply via email to