X-Git-Url: https://gerrit.fd.io/r/gitweb?a=blobdiff_plain;f=doc%2Fguides%2Fcontributing%2Fpatches.rst;h=daa4edada050702197e47c66d0517993fac671b3;hb=refs%2Fheads%2Fupstream-17.11-stable;hp=40983c15096de058d2a02d35b8ff44088e8cab51;hpb=6e7cbd63706f3435b9d9a2057a37db1da01db9a7;p=deb_dpdk.git
diff --git a/doc/guides/contributing/patches.rst b/doc/guides/contributing/patches.rst
index 40983c15..daa4edad 100644
--- a/doc/guides/contributing/patches.rst
+++ b/doc/guides/contributing/patches.rst
@@ -25,9 +25,9 @@ The DPDK development process has the following features:
* All sub-repositories are merged into main repository for ``-rc1`` and ``-rc2`` versions of the release.
* After the ``-rc2`` release all patches should target the main repository.
-The mailing list for DPDK development is `dev@dpdk.org `_.
-Contributors will need to `register for the mailing list `_ in order to submit patches.
-It is also worth registering for the DPDK `Patchwork `_
+The mailing list for DPDK development is `dev@dpdk.org `_.
+Contributors will need to `register for the mailing list `_ in order to submit patches.
+It is also worth registering for the DPDK `Patchwork `_
The development process requires some familiarity with the ``git`` version control system.
Refer to the `Pro Git Book `_ for further information.
@@ -104,7 +104,7 @@ main repository::
git clone git://dpdk.org/dpdk
git clone http://dpdk.org/git/dpdk
-sub-repositories (`list `_)::
+sub-repositories (`list `_)::
git clone git://dpdk.org/next/dpdk-next-*
git clone http://dpdk.org/git/next/dpdk-next-*
@@ -418,7 +418,7 @@ If the patch is in relation to a previous email thread you can add it to the sam
git send-email --to dev@dpdk.org --in-reply-to <1234-foo@bar.com> 000*.patch
The Message ID can be found in the raw text of emails or at the top of each Patchwork patch,
-`for example `_.
+`for example `_.
Shallow threading (``--thread --no-chain-reply-to``) is preferred for a patch series.
Once submitted your patches will appear on the mailing list and in Patchwork.