From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: master updated (31e8500b061 -> 04e8ad6489e)
Date: Fri, 13 Sep 2024 15:54:35 +0200 [thread overview]
Message-ID: <87v7yzk6as.fsf@gmail.com> (raw)
In-Reply-To: <86frq3k79j.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 13 Sep 2024 16:33:44 +0300")
>>>>> On Fri, 13 Sep 2024 16:33:44 +0300, Eli Zaretskii <eliz@gnu.org> said:
>> From: Robert Pluim <rpluim@gmail.com>
>> Cc: emacs-devel@gnu.org
>> Date: Fri, 13 Sep 2024 14:36:52 +0200
>>
>> >>>>> On Fri, 13 Sep 2024 14:09:20 +0200, Robert Pluim <rpluim@gmail.com> said:
>>
>> BTW, is it worth updating admin/unicode/README? I can do that.
Eli> I guess so, but please either make it so the file doesn't need to be
Eli> updated each time we import a new Unicode version, or if that is
Eli> impossible, add to admin/notes/unicode some verbiage to the effect
Eli> that README should be updated.
I can make the URLs point to the latest version of the files easily
enough, but it also contains the dates of those files. All of them
with the exception of UnicodeData.txt have comments in them containing
those dates anyway, so I think we can just remove the dates from
README.
Robert
--
next prev parent reply other threads:[~2024-09-13 13:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <172616480089.7302.12250649684752047951@vcs2.savannah.gnu.org>
2024-09-13 8:18 ` master updated (31e8500b061 -> 04e8ad6489e) Robert Pluim
2024-09-13 10:52 ` Eli Zaretskii
2024-09-13 12:09 ` Robert Pluim
2024-09-13 12:36 ` Robert Pluim
2024-09-13 13:33 ` Eli Zaretskii
2024-09-13 13:54 ` Robert Pluim [this message]
2024-09-13 14:46 ` Eli Zaretskii
2024-09-13 15:11 ` Robert Pluim
2024-09-18 19:25 ` John ff
2024-09-13 13:29 ` 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=87v7yzk6as.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=eliz@gnu.org \
--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.