It seems that there's a style here that every title has a separate link target even if it's never used. Maybe there is some reason for that (maybe it should be explained in the documentation style document?), but if not then it seems reasonable to leave out the unused ones since they look to me like just visual clutter.
Signed-off-by: Ben Pfaff <[email protected]> --- Documentation/topics/testing.rst | 12 ------------ 1 file changed, 12 deletions(-) diff --git a/Documentation/topics/testing.rst b/Documentation/topics/testing.rst index 365416586a94..498aea4d0ae1 100644 --- a/Documentation/topics/testing.rst +++ b/Documentation/topics/testing.rst @@ -38,8 +38,6 @@ described in :doc:`/intro/install/general`. You do not need to install Open vSwitch or to build or load the kernel module to run these test suites. You do not need supervisor privilege to run these test suites. -.. _testing-unit-tests: - Unit Tests ~~~~~~~~~~ @@ -126,8 +124,6 @@ All the same options are available via TESTSUITEFLAGS. You may find that the valgrind results are easier to interpret if you put ``-q`` in ``~/.valgrindrc``, since that reduces the amount of output. -.. _testing-oftest: - OFTest ~~~~~~ @@ -181,8 +177,6 @@ standard and other standards. of Open vSwitch and OFTest in your bug report, plus any other information needed to reproduce the problem. -.. _ryu: - Ryu ~~~ @@ -211,8 +205,6 @@ omit ``RYUDIR`` of Open vSwitch and Ryu in your bug report, plus any other information needed to reproduce the problem. -.. _datapath-testing: - Datapath testing ~~~~~~~~~~~~~~~~ @@ -342,8 +334,6 @@ You should invoke scan-view to view analysis results. The last line of output from ``clang-analyze`` will list the command (containing results directory) that you should invoke to view the results on a browser. -.. _testing-ci: - Continuous Integration with Travis CI ------------------------------------- @@ -384,8 +374,6 @@ Instructions to setup travis-ci for your GitHub repository: 4. Pushing a commit to the repository which breaks the build or the testsuite will now trigger a email sent to [email protected] -.. _testing-vsperf: - vsperf ------ -- 2.10.2 _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
