From: Yuan Fu <casouri@gmail.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, Richard Stallman <rms@gnu.org>,
njackson@posteo.net, emacs-devel@gnu.org
Subject: Re: Help testing emacs-28.3-rc1.tar.gz on MS-Windows
Date: Thu, 2 Mar 2023 22:00:22 -0800 [thread overview]
Message-ID: <CCE46F99-8AB5-4479-9D42-32FEC15E018A@gmail.com> (raw)
In-Reply-To: <CADwFkmku4g_paBjGbBdexjMEay8YKWj=cP3D9X2Fwmj7BvZvpg@mail.gmail.com>
> On Feb 19, 2023, at 9:11 AM, Stefan Kangas <stefankangas@gmail.com> wrote:
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
>> Unfortunately, I think we must update all of them, for legal reasons.
>> Let's ask Richard.
>
> OK, let's see what he has to say. Meanwhile, I've updated the copyright
> years, and I'm preparing a new tarball as we speak.
>
I have excellent news for you: https://hynek.me/til/copyright-years/
Yuan
next prev parent reply other threads:[~2023-03-03 6:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-19 10:51 Help testing emacs-28.3-rc1.tar.gz on MS-Windows Stefan Kangas
2023-02-19 12:05 ` lux
2023-02-19 12:34 ` Stefan Kangas
2023-02-19 16:04 ` lux
2023-02-19 12:20 ` Eli Zaretskii
2023-02-19 12:34 ` Stefan Kangas
2023-02-19 12:39 ` lux
2023-02-19 13:05 ` Stefan Kangas
2023-02-19 13:49 ` N. Jackson
2023-02-19 14:06 ` Stefan Kangas
2023-02-19 15:00 ` Eli Zaretskii
2023-02-19 17:11 ` Stefan Kangas
2023-03-03 6:00 ` Yuan Fu [this message]
2023-03-03 7:57 ` Eli Zaretskii
2023-03-05 4:05 ` Richard Stallman
2023-08-19 18:14 ` Eli Zaretskii
2023-08-22 1:06 ` Richard Stallman
2023-08-22 11:40 ` Eli Zaretskii
2023-08-23 2:14 ` Richard Stallman
2023-02-19 15:31 ` Ulrich Mueller
2023-02-19 15:34 ` Eli Zaretskii
2023-02-19 15:05 ` Ulrich Mueller
2023-02-19 16:29 ` Stefan Kangas
2023-03-02 18:52 ` Troy Hinckley
2023-02-19 15:59 ` Óscar Fuentes
2023-02-19 19:05 ` Óscar Fuentes
2023-03-06 19:40 ` H. Dieter Wilhelm
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=CCE46F99-8AB5-4479-9D42-32FEC15E018A@gmail.com \
--to=casouri@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=njackson@posteo.net \
--cc=rms@gnu.org \
--cc=stefankangas@gmail.com \
/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).