unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: guix-patches--- via <guix-patches@gnu.org>
To: 66258@debbugs.gnu.org
Cc: "Raphaël Mélotte" <raphael.melotte@mind.be>
Subject: [bug#66258] [PATCH] doc: suggest using pre-inst-env for git-send-email on foreign distros
Date: Thu, 28 Sep 2023 15:58:03 +0200	[thread overview]
Message-ID: <1f5ec2f97a7eff5980d37904369f3c835a7844c3.1695909293.git.raphael.melotte@mind.be> (raw)

On foreign distros, not using pre-inst-env when using git-send-email results
in a backtrace ending with: no code for module (guix ui)
This can be confusing as users did not have to use pre-inst-env to use
git-send-email before.

* doc/contributing.texi (Sending a Patch Series): add a note to suggest using
pre-inst-env when calling git-send-email on foreign distros.
---
 doc/contributing.texi | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/doc/contributing.texi b/doc/contributing.texi
index 0de47a403b..c0676e28fa 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -1574,6 +1574,11 @@ Sending a Patch Series
 you can invoke it via the @command{etc/teams.scm help} command.  For
 more information regarding teams, see @xref{Teams}.
 
+@quotation Note
+On foreign distros, you might have to use @command{./pre-inst-env git
+send-email} for @file{etc/teams.scm} to work.
+@end quotation
+
 @unnumberedsubsubsec Multiple Patches
 @anchor{Multiple Patches}
 @cindex cover letter

base-commit: ce0cc6137df81919389f61671096a6ce701c0889
-- 
2.41.0





             reply	other threads:[~2023-09-28 13:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-28 13:58 guix-patches--- via [this message]
2023-12-11 22:16 ` bug#66258: [PATCH] doc: suggest using pre-inst-env for git-send-email on foreign distros Ludovic Courtès

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=1f5ec2f97a7eff5980d37904369f3c835a7844c3.1695909293.git.raphael.melotte@mind.be \
    --to=guix-patches@gnu.org \
    --cc=66258@debbugs.gnu.org \
    --cc=raphael.melotte@mind.be \
    /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).