bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org, Collin Funk <collin.funk1@gmail.com>
Subject: Re: [PATCH] gnulib-tool.py: Comment out undefined variable.
Date: Wed, 21 Feb 2024 18:29:54 +0100	[thread overview]
Message-ID: <5988287.9z1YWOviru@nimes> (raw)
In-Reply-To: <9a1409b7-27bc-4c46-af40-c9bc41cccfaf@gmail.com>

Collin Funk wrote:
> It seems that your commit 01cd78f9d682ff75cc5ab1c2d21b911bdd9215b8
> accidentally caused this. While cleaning up the handling of paths, I
> think you accidentally removed this variable.

Yep. Thanks for the fix! Applied.


      reply	other threads:[~2024-02-21 17:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-21 11:36 [PATCH] gnulib-tool.py: Comment out undefined variable Collin Funk
2024-02-21 16:08 ` Bruno Haible
2024-02-21 17:17   ` Collin Funk
2024-02-21 17:29     ` Bruno Haible [this message]

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:

  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=5988287.9z1YWOviru@nimes \
    --to=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=collin.funk1@gmail.com \


* 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).