[gentoo-commits] repo/proj/guru:dev commit in: /

["Alessandro Barbieri" <lssndrbarbieri@gmail.com>]

commit:     f8caf432510f5a226f59b82de5b024cc50d2fe32
Author:     Alessandro Barbieri <lssndrbarbieri <AT> gmail <DOT> com>
AuthorDate: Sun Jul 25 23:49:31 2021 +0000
Commit:     Alessandro Barbieri <lssndrbarbieri <AT> gmail <DOT> com>
CommitDate: Sun Jul 25 23:49:31 2021 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=f8caf432

CONTRIBUTING.md: mention the clean patch guide

Closes: https://github.com/gentoo/guru/issues/28
Signed-off-by: Alessandro Barbieri <lssndrbarbieri <AT> gmail.com>

 CONTRIBUTING.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 0fcc70708..2719cc93b 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -87,3 +87,7 @@ See the [dev manual](https://devmanual.gentoo.org/eclass-reference/distutils-r1.
 Installation of small files, like documentation, completions, man pages, etc, does not have to be toggle-able with an USE flag. Instead, just install these files unconditionally. This avoids unnecessary recompilations when an user forgot to enable a flag that installs a small file.
 
 The same holds for optional runtime dependencies. It is not necessary to introduce a USE flag, that does not alter the compiled binary and just pulls in an extra optional runtime dependency. Instead, you can notify the user of these optional runtime dependencies with the `optfeature` function from the [optfeature](https://devmanual.gentoo.org/eclass-reference/optfeature.eclass/) eclass (early from currently deprecated [eutils](https://devmanual.gentoo.org/eclass-reference/eutils.eclass/) eclass). If, for whatever reason, it is still desired to introduce an USE flag for optional runtime dependencies, one can still use the `optfeature` function as well to allow the user to choose to avoid recompiling a package.
+
+- #### Clean your patches
+
+See the [dev manual](https://devmanual.gentoo.org/ebuild-writing/misc-files/patches/#clean-patch-howto) for a guide on how to write clean patches