From: lux <lx@shellcodes.org>
To: Stefan Kangas <stefankangas@gmail.com>, Eli Zaretskii <eliz@gnu.org>
Cc: rms@gnu.org, theophilusx@gmail.com, emacs-devel@gnu.org
Subject: Re: Request to backport fix for CVE-2022-45939 to Emacs 28
Date: Sat, 18 Feb 2023 01:37:04 +0800 [thread overview]
Message-ID: <tencent_CB86AB86A966ECCE4C3E287C31F880536805@qq.com> (raw)
In-Reply-To: <CADwFkmmuOzsT2MHme4YaG-tJbupZ+7C7Qec_R73ris3bzqGthA@mail.gmail.com>
On Fri, 2023-02-17 at 06:01 -0800, Stefan Kangas wrote:
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > The tarball needs to be test-built on the main platforms we care
> > about, and the diffs against the Emacs 28.2 tarball carefully
> > eyeballed to make sure nothing is amiss.
>
> Thanks.
>
> I can test the tarball on GNU/Linux and macOS. Could someone please
> volunteer to help test build it on other platforms (such as MS-
> Windows)?
>
I can compile normally in Windows 10+MINGW64：
$ uname -a
MINGW64_NT-10.0-19044 lx-windows 3.4.5.x86_64 2023-01-20 09:17 UTC
x86_64 Msys
$ ./emacs/src/emacs --version
GNU Emacs 28.3
Copyright (C) 2022 Free Software Foundation, Inc.
GNU Emacs comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of GNU Emacs
under the terms of the GNU General Public License.
For more information about these matters, see the file named COPYING.
next prev parent reply other threads:[~2023-02-17 17:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <85f35c42-cfe8-44a7-a9c1-307acc5c17d4@Spark>
2023-02-13 18:15 ` Request to backport fix for CVE-2022-45939 to Emacs 28 Troy Hinckley
2023-02-13 20:47 ` Eli Zaretskii
2023-02-14 5:07 ` lux
2023-02-14 13:19 ` Eli Zaretskii
2023-02-14 16:09 ` Troy Hinckley
2023-02-14 17:04 ` Eli Zaretskii
2023-02-17 1:44 ` Lynn Winebarger
2023-02-17 2:35 ` lux
2023-02-14 20:10 ` Tim Cross
2023-02-15 8:32 ` Robert Pluim
2023-02-18 4:19 ` Richard Stallman
2023-02-15 12:28 ` Eli Zaretskii
2023-02-16 17:50 ` Richard Stallman
2023-02-16 20:02 ` Eli Zaretskii
2023-02-16 20:41 ` Jim Porter
2023-02-16 20:52 ` Eli Zaretskii
2023-02-17 10:26 ` Stefan Kangas
2023-02-17 10:38 ` Robert Pluim
2023-02-17 12:33 ` Eli Zaretskii
2023-02-17 14:01 ` Stefan Kangas
2023-02-17 17:37 ` lux [this message]
2023-02-18 6:54 ` lux
2023-02-19 20:33 ` Corwin Brust
2023-02-21 14:54 ` Michael Albinus
2023-02-19 4:47 ` Richard Stallman
2023-02-19 7:05 ` Eli Zaretskii
2023-02-14 8:13 ` Robert Pluim
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=tencent_CB86AB86A966ECCE4C3E287C31F880536805@qq.com \
--to=lx@shellcodes.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=stefankangas@gmail.com \
--cc=theophilusx@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).