bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Collin Funk <collin.funk1@gmail.com>
To: Bruno Haible <bruno@clisp.org>, bug-gnulib@gnu.org
Subject: Re: hash_delete safe to remove?
Date: Sat, 13 Apr 2024 18:05:39 -0700	[thread overview]
Message-ID: <b2151a43-6e67-4709-8784-293b31f3c708@gmail.com> (raw)
In-Reply-To: <52700683.3TNR287u6W@nimes>

On 4/13/24 5:50 PM, Bruno Haible wrote:
> Has there been an official 'patch' release that includes the change,
> already? If not, it's too early: Some people (or distros) like to
> take the git checkout of the latest release and rebuild the generated
> files with the newest gnulib. There will be some things to update, sure
> (like the 'execute' argument list). But the fewer problems there are,
> the better. Even if we don't promise that there are no problems.

That makes sense. Thanks for the explanation. No there hasn't been a
release yet. My original reason for updating Gnulib there was build
errors that were fixed in a subsequent commit [1]. That also involved
updating the argument list to 'execute'.

> In other words: Each backward-incompatible change (-> mentioned in the
> NEWS file) can trigger problems. Let's try to minimize the trouble.

Sounds good.

[1] https://lists.gnu.org/archive/html/bug-patch/2024-02/msg00000.html

Collin


      reply	other threads:[~2024-04-14  1:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-13 19:50 hash_delete safe to remove? Collin Funk
2024-04-14  0:50 ` Bruno Haible
2024-04-14  1:05   ` 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=b2151a43-6e67-4709-8784-293b31f3c708@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).