bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
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 10:37:27 -0800	[thread overview]
Message-ID: <875xyk2tco.fsf@gmail.com> (raw)
In-Reply-To: <10243767.qOBuL9xsDt@nimes> (Bruno Haible's message of "Mon, 19 Feb 2024 03:17:26 +0100")

Bruno Haible <bruno@clisp.org> writes:
> The status: It's about 2/3 complete. 4 months of work have gone into it,
> and 2 months of work still remaining. (That's my estimation, based on
> two weeks of work that I put in, in 2022.)
> 65% of the .py code has been verified to be in sync with the bash code;
> 35% still to go. And then, the changes from the gnulib-tool.py.TODO list

I see. I had it open and compared some of it to the shell script and it
wasn't too hard to follow. Maybe I could help hack away at some of in my
free time.

I assume the best way to test it would be to create a small test
directory with a few modules? I think all of the header file
replacements would break the build so whichever ones avoid using those.


  parent reply	other threads:[~2024-02-19 18:37 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   ` Collin Funk [this message]
2024-02-19 21:36     ` [PATCH] gnulib-tool.py: Fix function call on incorrect object Bruno Haible
2024-02-19 22:42       ` Collin Funk

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=875xyk2tco.fsf@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).