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 "UNNAMED PROJECT".
The branch, neels/doc has been created
at d2e793a58aceb19fea1d29b550894407331fea7f (commit)
- Log -----------------------------------------------------------------
http://cgit.osmocom.org/python/osmo-python-tests/commit/?id=d2e793a58aceb19…
commit d2e793a58aceb19fea1d29b550894407331fea7f
Author: Neels Hofmeyr <neels(a)hofmeyr.de>
Date: Mon Sep 18 16:00:21 2017 +0200
osmodumpdoc: print generated path
Change-Id: Ie39316f0b51ee518b9dce8d5f98b53f748db573b
http://cgit.osmocom.org/python/osmo-python-tests/commit/?id=a784f2407b087e1…
commit a784f2407b087e17ba4a6447e4f1b5cf6c524e22
Author: Neels Hofmeyr <neels(a)hofmeyr.de>
Date: Mon Sep 18 16:02:55 2017 +0200
osmodumpdoc: print called commands and OSError messages
Change-Id: Ib044cbb8a1b8e02cbe6852f785c75b5c7aae6174
http://cgit.osmocom.org/python/osmo-python-tests/commit/?id=8e4806c5f20f082…
commit 8e4806c5f20f082c911f5a95d88c5fdd2c26d58b
Author: Neels Hofmeyr <neels(a)hofmeyr.de>
Date: Mon Sep 18 16:01:44 2017 +0200
osmodumpdoc: fix finding cfg when not calling from source tree
When the binary has not been built in the source tree, it was impossible to
call osmodumpdoc.py despite the -p <config-path> option. Look for config files
in that config-path.
Make sure a relative config-path is adjusted when changing to the workdir.
Change-Id: I5427d354c289ec4602411c7059c8d80e2b451f7c
-----------------------------------------------------------------------
hooks/post-receive
--
UNNAMED PROJECT