bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Cc: Collin Funk <collin.funk1@gmail.com>
Subject: Re: gnulib-tool.py: Follow gnulib-tool changes, part 29, 30.
Date: Tue, 27 Feb 2024 11:36:07 +0100	[thread overview]
Message-ID: <5605830.atdPhlSkOF@nimes> (raw)
In-Reply-To: <ffaffc17-4727-4fff-be98-4860e33b23a1@gmail.com>

Collin Funk wrote:
> These two TODO entries were pretty simple. One of the ChangeLog
> entries listed to a test case Bruno wrote that worked for testing both
> of them.
> 
> [collin@debian gnulib]$ gnulib-tool.py --create-testdir --dir=testdir-all --single-configure
> module parse-datetime2 depends on a module with an incompatible license: gettime
> module parse-datetime2 depends on a module with an incompatible license: nstrftime
> module parse-datetime2 depends on a module with an incompatible license: parse-datetime
> module parse-datetime2 depends on a module with an incompatible license: time_rz
> module parse-datetime2 depends on a module with an incompatible license: timespec
> module parse-datetime2 depends on a module with an incompatible license: tzset
> module ucs4-utf16 depends on a module with an incompatible license: unistr/u16-uctomb
> module utf16-ucs4 depends on a module with an incompatible license: unistr/u16-mbtouc
> module utf16-ucs4-unsafe depends on a module with an incompatible license: unistr/u16-mbtouc-unsafe
> 
> The first patch fixes the parse-datetime2 warnings in the same way
> that gnulib-tool does (ready for the release of parse-datetime3). The
> second fixes the libunistring ones. Let me know if I missed anything.

Thanks! Applied both patches.

Bruno





      parent reply	other threads:[~2024-02-27 10:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-27  6:04 gnulib-tool.py: Follow gnulib-tool changes, part 29, 30 Collin Funk
2024-02-27 10:16 ` gnulib-tool.py: Follow gnulib-tool changes, part 31 Collin Funk
2024-02-27 10:53   ` Bruno Haible
2024-02-27 10:36 ` 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:
  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=5605830.atdPhlSkOF@nimes \
    --to=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=collin.funk1@gmail.com \
    /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).