From: Collin Funk <collin.funk1@gmail.com>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib@gnu.org
Subject: Re: [PATCH] gnulib-tool.py: Fix function call on incorrect object.
Date: Mon, 19 Feb 2024 14:42:29 -0800 [thread overview]
Message-ID: <22dc9f1d-2339-4b0f-bffa-309e0b36afae@gmail.com> (raw)
In-Reply-To: <4603648.7YbXXFKy9f@nimes>
On 2/19/24 1:36 PM, Bruno Haible wrote:
> You don't need to go to the './configure' and 'make' stages at this point.
> Just ensuring that the outputs of gnulib-tool and gnulib-tool.py are the
> same will sufficiently guide you.
Ah, I see. Thanks for this and the rest of the advice.
Collin
prev parent reply other threads:[~2024-02-19 22:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 1:24 [PATCH] gnulib-tool.py: Fix function call on incorrect object Collin Funk
2024-02-19 2:17 ` Bruno Haible
2024-02-19 8:59 ` Simon Josefsson via Gnulib discussion list
2024-02-19 10:38 ` gnulib-tool caching Bruno Haible
2024-02-19 12:55 ` Simon Josefsson via Gnulib discussion list
2024-02-19 21:50 ` Bruno Haible
2024-02-19 22:24 ` Sam James
2024-02-19 23:11 ` Bruno Haible
2024-02-19 23:17 ` Sam James
2024-02-19 18:37 ` [PATCH] gnulib-tool.py: Fix function call on incorrect object Collin Funk
2024-02-19 21:36 ` Bruno Haible
2024-02-19 22:42 ` Collin Funk [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:
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=22dc9f1d-2339-4b0f-bffa-309e0b36afae@gmail.com \
--to=collin.funk1@gmail.com \
--cc=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).