doc/guides/contributing/patches.rst: corrected typing mistake in line 185
Checks
Commit Message
Bugzilla ID: 422
Cc: marko.kovacevic@intel.com
Cc: john.mcnamara@intel.com
Cc: dev@dpdk.org
Cc: stable@dpdk.org
Signed-off-by: Muhammad Bilal <m.bilal@emumba.com>
---
doc/guides/contributing/patches.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Comments
26/03/2020 06:46, Muhammad Bilal:
> Bugzilla ID: 422
> Cc: marko.kovacevic@intel.com
> Cc: john.mcnamara@intel.com
> Cc: dev@dpdk.org
> Cc: stable@dpdk.org
> Signed-off-by: Muhammad Bilal <m.bilal@emumba.com>
> ---
> --- a/doc/guides/contributing/patches.rst
> +++ b/doc/guides/contributing/patches.rst
> -file as the code, rather than one big documentation patch at then end of a
> +file as the code, rather than one big documentation patch at the end of a
Fixes: 9e0e4a00df77 ("doc: suggest to keep doc and code in same patch")
Applied, thanks
@@ -182,7 +182,7 @@ A good way of thinking about whether a patch should be split is to consider whet
applied without dependencies as a backport.
It is better to keep the related documentation changes in the same patch
-file as the code, rather than one big documentation patch at then end of a
+file as the code, rather than one big documentation patch at the end of a
patchset. This makes it easier for future maintenance and development of the
code.