diff options
| author | Stephen Finucane <stephen@that.guru> | 2016-12-23 23:04:11 +0000 |
|---|---|---|
| committer | Ben Pfaff <blp@ovn.org> | 2016-12-23 16:11:46 -0800 |
| commit | 34aa9cf97e2c5c937296012183dea5862a2b6190 (patch) | |
| tree | 400fe488fc695a9de805deb05edc2df39cd6f9c6 /Documentation/internals | |
| parent | cfa354cb62f19ea15bf3e1508d2eb63f3c7223d4 (diff) | |
| download | openvswitch-34aa9cf97e2c5c937296012183dea5862a2b6190.tar.gz | |
docs: Resolve broken URLs
These were found using the 'linkcheck' builder.
Signed-off-by: Stephen Finucane <stephen@that.guru>
Cc: Ben Pfaff <blp@ovn.org>
Signed-off-by: Ben Pfaff <blp@ovn.org>
Diffstat (limited to 'Documentation/internals')
4 files changed, 14 insertions, 13 deletions
diff --git a/Documentation/internals/contributing/coding-style.rst b/Documentation/internals/contributing/coding-style.rst index 84100640e..e62f5e343 100644 --- a/Documentation/internals/contributing/coding-style.rst +++ b/Documentation/internals/contributing/coding-style.rst @@ -638,5 +638,5 @@ Python ------ When introducing new Python code, try to follow Python's `PEP 8 -<http://www.python.org/dev/peps/pep-0008/>`__ style. Consider running the +<https://www.python.org/dev/peps/pep-0008/>`__ style. Consider running the ``pep8`` or ``flake8`` tool against your code to find issues. diff --git a/Documentation/internals/contributing/documentation-style.rst b/Documentation/internals/contributing/documentation-style.rst index ef0e0e751..ea41a07e6 100644 --- a/Documentation/internals/contributing/documentation-style.rst +++ b/Documentation/internals/contributing/documentation-style.rst @@ -365,4 +365,4 @@ Useful Links - `Quick reStructuredText <http://docutils.sourceforge.net/docs/user/rst/quickref.html>`__ -- `Sphinx Documentation <http://sphinx.readthedocs.org/en/latest/rest.html>`__ +- `Sphinx Documentation <http://sphinx.readthedocs.io/en/latest/rest.html>`__ diff --git a/Documentation/internals/contributing/submitting-patches.rst b/Documentation/internals/contributing/submitting-patches.rst index 9fb7785cd..36e3b1795 100644 --- a/Documentation/internals/contributing/submitting-patches.rst +++ b/Documentation/internals/contributing/submitting-patches.rst @@ -402,9 +402,9 @@ not want to use Git. Patches should be inline in the email message. Some email clients corrupt white space or wrap lines in patches. There are hints on how to configure many email clients to avoid this problem on `kernel.org -<http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob_plain;f=Documentation/email-clients.txt>`__. -If you cannot convince your email client not to mangle patches, then sending -the patch as an attachment is a second choice. +<https://static.lwn.net/kerneldoc/process/email-clients.html>`__. If you +cannot convince your email client not to mangle patches, then sending the patch +as an attachment is a second choice. Follow the style used in the code that you are modifying. :doc:`coding-style` file describes the coding style used in most of Open vSwitch. Use Linux kernel diff --git a/Documentation/internals/security.rst b/Documentation/internals/security.rst index 806221111..da7b9b0f8 100644 --- a/Documentation/internals/security.rst +++ b/Documentation/internals/security.rst @@ -89,12 +89,12 @@ Consider reporting the information mentioned in :doc:`bugs`, where relevant. Reporters may ask for a GPG key while initiating contact with the security team to deliver more sensitive reports. -The Linux kernel has its own vulnerability management process: -https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/SecurityBugs -Handling of vulnerabilities that affect both the Open vSwitch tree and the -upstream Linux kernel should be reported through both processes. Send your -report as a single email to both the kernel and OVS security teams to allow -those teams to most easily coordinate among themselves. +The Linux kernel has `its own vulnerability management process +<https://static.lwn.net/kerneldoc/admin-guide/security-bugs.html>`__. Handling +of vulnerabilities that affect both the Open vSwitch tree and the upstream +Linux kernel should be reported through both processes. Send your report as a +single email to both the kernel and OVS security teams to allow those teams to +most easily coordinate among themselves. Step 2: Assessment ------------------ @@ -220,8 +220,9 @@ sections for the document include: Certificate of Origin. It should also include other appropriate tags, such as Acked-by tags obtained during review. -CVE-2016-2074 is an example advisory document, available at: -http://openvswitch.org/pipermail/announce/2016-March/000082.html +`CVE-2016-2074 +<https://mail.openvswitch.org/pipermail/ovs-announce/2016-March/000082.html>`__ +is an example advisory document. Step 3b: Fix ------------ |