unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Stefan Monnier <monnier@iro.umontreal.ca>, Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: master 5b13afa: Update publicsuffix.txt from upstream
Date: Fri, 16 Oct 2020 13:08:58 -0700	[thread overview]
Message-ID: <CADwFkm=gHfEktDYXjwwqQc87n+sWpe4nrYL1bKD0e9uRCEWQ8A@mail.gmail.com> (raw)
In-Reply-To: <jwvft6euwl2.fsf-monnier+emacs@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 495 bytes --]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> How many of us are sufficiently aware of this publicsuffix.txt copy we
> have?  Are there enough of us to make sure we won't end up forgetting
> about it some day?

FWIW, I've added it to my Emacs todo-list as a recurring item, so I've
effectively adopted this particular stray cat.

Of course, it's still a good idea to put other measures in place.  For
example, the attached patch adds a note to update some files to
admin/release-process.

[-- Attachment #2: 0001-admin-release-process-Add-note-to-update-files-from-.patch --]
[-- Type: text/x-diff, Size: 980 bytes --]

From 594a421b945070650f3d9498720486630b2d0648 Mon Sep 17 00:00:00 2001
From: Stefan Kangas <stefan@marxist.se>
Date: Fri, 16 Oct 2020 21:51:48 +0200
Subject: [PATCH] * admin/release-process: Add note to update files from
 upstream.

---
 admin/release-process | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/admin/release-process b/admin/release-process
index 73879b13f0..4d973d3361 100644
--- a/admin/release-process
+++ b/admin/release-process
@@ -195,6 +195,17 @@ pt-br	Rodrigo Real
 ru	Alex Ott
 sk	Miroslav Vaško
 
+** Update some files from their upstream.
+
+Some files in Emacs are copies of data files maintained elsewhere.
+Make sure that they are reasonably up-to-date.
+
+- etc/publicsuffix.txt
+https://publicsuffix.org/list/public_suffix_list.dat
+
+- leim/SKK-DIC/SKK-JISYO.L
+https://raw.githubusercontent.com/skk-dev/dict/master/SKK-JISYO.L
+
 * BUGS
 
 ** Check for modes which bind M-s that conflicts with a new global binding M-s
-- 
2.28.0


  parent reply	other threads:[~2020-10-16 20:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20201011131732.10940.57772@vcs0.savannah.gnu.org>
     [not found] ` <20201011131733.C038620619@vcs0.savannah.gnu.org>
2020-10-11 18:48   ` master 5b13afa: Update publicsuffix.txt from upstream Stefan Monnier
2020-10-16  9:24     ` Stefan Kangas
2020-10-16 10:30       ` Eli Zaretskii
2020-10-16 13:33         ` Stefan Monnier
2020-10-16 19:25           ` Eli Zaretskii
2020-10-16 20:08           ` Stefan Kangas [this message]
2020-10-16 22:30             ` Stefan Monnier
2020-10-17  0:07               ` Stefan Kangas

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='CADwFkm=gHfEktDYXjwwqQc87n+sWpe4nrYL1bKD0e9uRCEWQ8A@mail.gmail.com' \
    --to=stefan@marxist.se \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).