>From 0e84643a50d578b6b5bb68119b35dc92d90dafd5 Mon Sep 17 00:00:00 2001
From: ng0 <n...@we.make.ritual.n0.is>
Date: Thu, 21 Jul 2016 13:24:36 +0000
Subject: [PATCH 2/3] doc: Send changes in your patch which are related.
* doc/contributing.texi (Submitting Patches): New @item:
This gives information about sending related changes and examples on
what we view as related changes.
---
doc/contributing.texi | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/doc/contributing.texi b/doc/contributing.texi
index b6f9771..323fcaa 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -323,6 +323,21 @@ related to the hardware---e.g., use of different
instruction set
extensions---or to the operating system kernel---e.g., reliance on
@code{uname} or @file{/proc} files.
+@item
+Send changes in your patch which are related. If you send several
+unrelated changes together, we will ask you to separate them so that we
+can work more efficiently on them. Bundling unrelated changes together
+in big patches makes reviewing harder and slows down the time to apply
+them.
+
+Examples for related changes are: You changed URLs from http to
+https in one file. You wrote a new service which required adding
+documentation about it. You discovered that a new version of an
+application was released and updated it, but this required new
+dependencies and small fixes.
+If you combine more than one example in one patch you get examples
+for what we understand as mixing changes.
+
@end enumerate
When posting a patch to the mailing list, use @samp{[PATCH] @dots{}} as
--
2.9.1
--
♥Ⓐ ng0 – http://we.make.ritual.n0.is
For non-prism friendly talk find me on http://www.psyced.org
SecuShare – http://secushare.org
