all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: master bdb13a0e5c5 1/2: Adjust to Gnulib’s recent module renaming
Date: Thu, 02 Jan 2025 19:30:15 +0200	[thread overview]
Message-ID: <86a5c9jf88.fsf@gnu.org> (raw)
In-Reply-To: <mailman.2001.1735773573.32144.emacs-diffs@gnu.org> (emacs-diffs-request@gnu.org)

Paul,

Is there any chance to enhance admin/merge-gnulib so that if the
import renames some Gnulib modules, the renaming will be reflected in
nt/gnulib-cfg.mk?  Currently, such renaming needs to be caught in time
by someone who knows about nt/gnulib-cfg.mk, and then the
corresponding renames manually repeated there.  This is error-prone
and relies on approximately one person we have on board who knows
about these subtleties to pay attention.  Automation would go a long
way towards eliminating many issues due to such renaming.

There's also a similar problem with adding new modules.  Here, we need
a judgment call by an Emacs developer who is familiar with the w32
code, so I don't see how this could be automated.  However, sending a
heads-up email to this list by admin/merge-gnulib, if that is
feasible, could be a good-enough solution.

Can these enhancements be done, please?



       reply	other threads:[~2025-01-02 17:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.2001.1735773573.32144.emacs-diffs@gnu.org>
2025-01-02 17:30 ` Eli Zaretskii [this message]
2025-01-02 17:57   ` master bdb13a0e5c5 1/2: Adjust to Gnulib’s recent module renaming Stefan Kangas
2025-01-02 19:38     ` Paul Eggert
2025-01-02 20:30       ` Eli Zaretskii
2025-01-02 21:15         ` Paul Eggert
2025-01-03  6:42           ` Eli Zaretskii
2025-01-03 19:06             ` Paul Eggert
2025-01-03 20:01               ` Eli Zaretskii

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86a5c9jf88.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.