bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Subject: gnulib-tool.py: Fix output of --create-megatestdir
Date: Sat, 20 Apr 2024 21:56:10 +0200	[thread overview]
Message-ID: <6752110.7BTdM3MpAm@nimes> (raw)

This difference in output was highlighted by the sh+py mode:

diff -u tmp3271005-result/do-autobuild tmp3271005-result-glpy3271006/do-autobuild
--- tmp3271005-result/do-autobuild      2024-04-20 20:42:09.788152428 +0200
+++ tmp3271005-result-glpy3271006/do-autobuild  2024-04-20 20:41:12.699970866 +0200
@@ -5,7 +5,7 @@
 for module in fopen fopen-gnu ALL; do
   echo "Working on module $module..."
   safemodule=`echo $module | sed -e 's|/|-|g'`
-  (echo "To: gnulib@autobuild.josefsson.org"
+  (echo "To: gnulib@autobuild.josefsson.org"\
    echo
    set -x
    : autobuild project... $module


This patch fixes it.


2024-04-20  Bruno Haible  <bruno@clisp.org>

	gnulib-tool.py: Fix output of --create-megatestdir.
	* pygnulib/GLTestDir.py (GLMegaTestDir.execute): Remove stray backslash
	from output.

diff --git a/pygnulib/GLTestDir.py b/pygnulib/GLTestDir.py
index 38427e402e..6f74453f29 100644
--- a/pygnulib/GLTestDir.py
+++ b/pygnulib/GLTestDir.py
@@ -973,7 +973,7 @@ def execute(self) -> None:
         emit += 'for module in %s; do\n' % ' '.join(megasubdirs)
         emit += '  echo "Working on module $module..."\n'
         emit += '  safemodule=`echo $module | sed -e \'s|/|-|g\'`\n'
-        emit += '  (echo "To: gnulib@autobuild.josefsson.org"\\\n'
+        emit += '  (echo "To: gnulib@autobuild.josefsson.org"\n'
         emit += '   echo\n'
         emit += '   set -x\n'
         emit += '   : autobuild project... $module\n'





                 reply	other threads:[~2024-04-20 19:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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://lists.gnu.org/mailman/listinfo/bug-gnulib

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

  git send-email \
    --in-reply-to=6752110.7BTdM3MpAm@nimes \
    --to=bruno@clisp.org \
    --cc=bug-gnulib@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.
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).