unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Emacs-devel@gnu.org
Subject: Re: Including <locale.h> unconditionally in Emacs
Date: Wed, 5 Jun 2024 22:44:39 -0700	[thread overview]
Message-ID: <57488183-bd8f-44bd-89dd-c5b7376682fd@cs.ucla.edu> (raw)
In-Reply-To: <86plsuisdh.fsf@gnu.org>

On 2024-06-05 21:53, Eli Zaretskii wrote:

> I'd like to hear from Po Lu wrt the
> Andriod port, as I'm not familiar with the situation there.  I think
> Po Lu also builds Emacs on some ancient Solaris version, so maybe
> there's an issue there?  And what about macOS?

None of these are real issues. Android has had locale.h since day 1. 
Even ancient, ancient SunOS has it and besides, there's no point porting 
to anything older than Solaris 10 aka SunOS 5.10 (the oldest supported 
version). macOS has had it "forever" too.


> please don't make this change in Emacs until after the
> emacs-30 release branch is cut (which should happen soon).

Of course.


> we
> will have one more reason not to import from Gnulib before the branch
> point.

I can sync from Gnulib into the master branch after "soon" happens, and 
then people can copy those fixes into the emacs-30 branch if and when 
they feel the need. There's no rush. I wouldn't have even bothered to 
sync from Gnulib recently, except that somebody reported a 
Gnulib-related bug on the master branch.



  reply	other threads:[~2024-06-06  5:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-05 20:18 Including <locale.h> unconditionally in Emacs Paul Eggert
2024-06-06  4:53 ` Eli Zaretskii
2024-06-06  5:44   ` Paul Eggert [this message]
2024-06-06  5:57     ` Eli Zaretskii
2024-06-06  6:46       ` Po Lu
2024-06-06  7:02         ` Stefan Kangas
2024-06-23 12:32     ` Stefan Kangas
2024-06-23 12:38       ` Eli Zaretskii
2024-06-08  2:54 ` Richard Stallman
2024-06-08  6:46   ` Eli Zaretskii
2024-06-11 15:01     ` Richard Stallman
2024-06-23  9:16     ` Björn Bidar

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://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=57488183-bd8f-44bd-89dd-c5b7376682fd@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=Emacs-devel@gnu.org \
    --cc=eliz@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 public inbox

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

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).