summary refs log tree commit diff
path: root/doc
diff options
context:
space:
mode:
authorng0 <ng0@we.make.ritual.n0.is>2016-07-21 18:05:30 +0000
committerLudovic Courtès <ludo@gnu.org>2016-07-28 15:38:14 +0200
commit3a78fab83dd5faa80d8eecd792f40dde6e334c7c (patch)
tree9480e213051ee9c0692f5b0bd2a470988cfcdd98 /doc
parent189b1543cbc2db50e6dd309e84bce4eb503f0493 (diff)
downloadguix-3a78fab83dd5faa80d8eecd792f40dde6e334c7c.tar.gz
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.

Co-authored-by: Ludovic Courtès <ludo@gnu.org>
Diffstat (limited to 'doc')
-rw-r--r--doc/contributing.texi7
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/contributing.texi b/doc/contributing.texi
index 6496e10a14..a3684a5e1d 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -340,6 +340,13 @@ referring to people, such as
 @uref{https://en.wikipedia.org/wiki/Singular_they, singular
 ``they''@comma{} ``their''@comma{} ``them''}, and so forth.
 
+@item
+Verify that your patch contains only one set of related changes.
+Bundling unrelated changes together makes reviewing harder and slower.
+
+Examples of unrelated changes include the addition of several packages,
+or a package update along with fixes to that package.
+
 @end enumerate
 
 When posting a patch to the mailing list, use @samp{[PATCH] @dots{}} as