[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Request to backport fix for CVE-2022-45939 to Emacs 28
From: |
Eli Zaretskii |
Subject: |
Re: Request to backport fix for CVE-2022-45939 to Emacs 28 |
Date: |
Tue, 14 Feb 2023 19:04:55 +0200 |
> Date: Tue, 14 Feb 2023 10:09:43 -0600
> From: Troy Hinckley <comms@dabrev.com>
> Cc: emacs-devel@gnu.org
>
> If the commit was cherry picked to the emacs-28 branch, does that mean it’s
> just unreleased changes for
> Emacs 28?
Yes.
> We are building from source, so that might be enough. I didn’t realize
> cutting a release was high
> effort.
It's a non-trivial effort, yes.
- Request to backport fix for CVE-2022-45939 to Emacs 28, Troy Hinckley, 2023/02/13
- Re: Request to backport fix for CVE-2022-45939 to Emacs 28, Eli Zaretskii, 2023/02/15
- Re: Request to backport fix for CVE-2022-45939 to Emacs 28, Richard Stallman, 2023/02/16
- Re: Request to backport fix for CVE-2022-45939 to Emacs 28, Eli Zaretskii, 2023/02/16
- Re: Request to backport fix for CVE-2022-45939 to Emacs 28, Jim Porter, 2023/02/16
- Re: Request to backport fix for CVE-2022-45939 to Emacs 28, Eli Zaretskii, 2023/02/16