[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#38455] [PATCH] doc: Mention how to test against make / guix pull br
From: |
Pierre Neidhardt |
Subject: |
[bug#38455] [PATCH] doc: Mention how to test against make / guix pull breakage. |
Date: |
Mon, 2 Dec 2019 10:15:50 +0100 |
* doc/contributing.texi (Submitting Patches): Mention commands in the check
list.
---
doc/contributing.texi | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/doc/contributing.texi b/doc/contributing.texi
index ee72b2f94d..04a4ba3e1a 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -961,6 +961,16 @@ often better to clone the repository. Don't use the
@command{name} field in
the URL: it is not very useful and if the name changes, the URL will probably
be wrong.
+@item
+Make sure your changes do not break Guix: rebuild it with
+@example
+guix environment guix -- make
+@end example
+and simulate a @code{guix pull} with
+@example
+guix pull --url=/path/to/your/checkout --dry-run
+@end example
+
@end enumerate
When posting a patch to the mailing list, use @samp{[PATCH] @dots{}} as
--
2.23.0
- [bug#38455] [PATCH] doc: Mention how to test against make / guix pull breakage.,
Pierre Neidhardt <=
[bug#38455] [PATCH] doc: Mention how to test against make / guix pull breakage., Danny Milosavljevic, 2019/12/02