From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>, Richard Stallman <rms@gnu.org>
Cc: njackson@posteo.net, emacs-devel@gnu.org
Subject: Re: Help testing emacs-28.3-rc1.tar.gz on MS-Windows
Date: Sun, 19 Feb 2023 17:00:24 +0200 [thread overview]
Message-ID: <83r0ulwvhz.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmnwgozmwEWvD4WtQMYT6Lf8iOc3yTNEchXNLqerZnVKhQ@mail.gmail.com> (message from Stefan Kangas on Sun, 19 Feb 2023 06:06:24 -0800)
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Sun, 19 Feb 2023 06:06:24 -0800
> Cc: emacs-devel@gnu.org
>
> N. Jackson <njackson@posteo.net> writes:
>
> > When I build this tarball I get
> >
> > GNU Emacs 28.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.35, cairo version 1.17.6)
> > of 2023-02-19
> > Copyright (C) 2022 Free Software Foundation, Inc.
> >
> > which is last year.
> >
> > Also the README file (which has the version number for this release,
> > so presumably it has been modified) still has a 2022 copyright date.
>
> There are a gazillion files where the copyright date is 2022 instead of
> 2023, and I'd like to avoid going over all of them. Perhaps we could
> change just a few of them, however, if it's important and/or worth
> doing. Eli, WDYT?
Unfortunately, I think we must update all of them, for legal reasons.
Let's ask Richard.
Richard, am I right that we must update the copyright years on all of
the files in the Emacs 28.3 tarball, even though it is an emergency
security release?
next prev parent reply other threads:[~2023-02-19 15: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 [this message]
2023-02-19 17:11 ` Stefan Kangas
2023-03-03 6:00 ` Yuan Fu
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83r0ulwvhz.fsf@gnu.org \
--to=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 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.