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/gerrit-log@lists.osmocom.org/.
pespin gerrit-no-reply at lists.osmocom.orgpespin has submitted this change. ( https://gerrit.osmocom.org/c/osmo-gsm-tester/+/18757 )
Change subject: doc/manual: Fix links to nonexistent sections
......................................................................
doc/manual: Fix links to nonexistent sections
Change-Id: I8742fa9c41d3ab95d41e299179df19c3d1e0a65b
---
M doc/manuals/chapters/config.adoc
M doc/manuals/chapters/install.adoc
2 files changed, 7 insertions(+), 7 deletions(-)
Approvals:
Jenkins Builder: Verified
pespin: Looks good to me, approved
diff --git a/doc/manuals/chapters/config.adoc b/doc/manuals/chapters/config.adoc
index 18ff55d..b4e4a95 100644
--- a/doc/manuals/chapters/config.adoc
+++ b/doc/manuals/chapters/config.adoc
@@ -326,15 +326,15 @@
A 'resources.conf' is validated by the <<schema_resources,resources schema>>.
That means it is structured as a list of items for each resource type, where
-each item has one or more attributes -- for an example, see
-<<resources_conf_example>>.
+each item has one or more attributes -- looking for an example, see {app-name}
+subdirectory _doc/examples_.
Side note: at first sight it might make sense to the reader to rather structure
e.g. the 'ip_address' or 'arfcn' configuration as +
'"arfcn: GSM-1800: [512, 514, ...]"', +
-but the more verbose format is chosen to stay consistent with the general
-structure of resource configurations, which the resource allocation algorithm
-uses to resolve required resources according to their traits. These
+but the more verbose format is chosen in general to stay consistent with the
+general structure of resource configurations, which the resource allocation
+algorithm uses to resolve required resources according to their traits. These
configurations look cumbersome because they exhibit only one trait / a trait
that is repeated numerous times. No special notation for these cases is
available (yet).
diff --git a/doc/manuals/chapters/install.adoc b/doc/manuals/chapters/install.adoc
index 445b53c..0e48e9d 100644
--- a/doc/manuals/chapters/install.adoc
+++ b/doc/manuals/chapters/install.adoc
@@ -309,7 +309,7 @@
wide install, in which case you could omit the explicit PATH to
"$PWD/osmo-gsm-tester/src".
*** This assumes that there are configuration files for osmo-gsm-tester placed
- on the system (see <<config_paths>>).
+ on the system (see <<config_main>>).
*** If you'd like to check the behavior of test failures, you can uncomment the
line below "# debug" to produce a build failure on every run. Note that
this test typically produces a quite empty run result, since it launches no
@@ -687,4 +687,4 @@
----
NOTE: The configuration will be looked up in various places, see
-<<config_paths>>.
+<<config_main>>.
--
To view, visit https://gerrit.osmocom.org/c/osmo-gsm-tester/+/18757
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-gsm-tester
Gerrit-Branch: master
Gerrit-Change-Id: I8742fa9c41d3ab95d41e299179df19c3d1e0a65b
Gerrit-Change-Number: 18757
Gerrit-PatchSet: 1
Gerrit-Owner: pespin <pespin at sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: pespin <pespin at sysmocom.de>
Gerrit-MessageType: merged
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/gerrit-log/attachments/20200610/45a333a4/attachment.htm>