[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: |
zimoun |
Subject: |
[bug#38455] [PATCH] doc: Mention how to test against make / guix pull breakage. |
Date: |
Mon, 2 Dec 2019 13:08:07 +0100 |
Hi Pierre,
On Mon, 2 Dec 2019 at 10:16, Pierre Neidhardt <address@hidden> wrote:
> * doc/contributing.texi (Submitting Patches): Mention commands in the check
> list.
Nice!
I propose instead this wording. Because, I am not sure that building
Guix from source is really necessary to run/check "guix pull".
--8<---------------cut here---------------start------------->8---
diff --git a/doc/contributing.texi b/doc/contributing.texi
index ee72b2f94d..8001b0aef1 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -961,6 +961,15 @@ 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 @command{guix pull}:
+
+@example
+guix pull --dry-run --url=/path/to/your/checkout
+@end example
+
+(see @pxref{Invoking guix pull}).
+
@end enumerate
When posting a patch to the mailing list, use @samp{[PATCH] @dots{}} as
--8<---------------cut here---------------end--------------->8---
Hope that helps.
Cheers,
simon
[bug#38455] [PATCH] doc: Mention how to test against make / guix pull breakage., Danny Milosavljevic, 2019/12/02
[bug#38455] [PATCH] doc: Mention how to test against make / guix pull breakage., zimoun, 2019/12/03