unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Pierre Neidhardt <mail@ambrevar.xyz>
To: 38455@debbugs.gnu.org
Subject: [bug#38455] [PATCH] doc: Mention how to test against make / guix pull breakage.
Date: Mon,  2 Dec 2019 10:15:50 +0100	[thread overview]
Message-ID: <20191202091550.15132-1-mail@ambrevar.xyz> (raw)

* 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

             reply	other threads:[~2019-12-02  9:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-02  9:15 Pierre Neidhardt [this message]
2019-12-02 12:08 ` [bug#38455] [PATCH] doc: Mention how to test against make / guix pull breakage zimoun
2019-12-02 12:16   ` Pierre Neidhardt
2019-12-02 12:32     ` zimoun
2019-12-02 12:48       ` zimoun
2019-12-02 19:31 ` Danny Milosavljevic
2019-12-02 20:14   ` Pierre Neidhardt
2019-12-02 21:48     ` Danny Milosavljevic
2019-12-03 10:39       ` zimoun
2019-12-03 10:34   ` zimoun
2019-12-08 15:42     ` Pierre Neidhardt
2019-12-12 15:55       ` zimoun
2019-12-13 12:32         ` Pierre Neidhardt
2019-12-13 12:32           ` Pierre Neidhardt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191202091550.15132-1-mail@ambrevar.xyz \
    --to=mail@ambrevar.xyz \
    --cc=38455@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).