unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: theophilusx@gmail.com, emacs-devel@gnu.org
Subject: Re: Request to backport fix for CVE-2022-45939 to Emacs 28
Date: Sun, 19 Feb 2023 09:05:14 +0200	[thread overview]
Message-ID: <83edqmxhhx.fsf@gnu.org> (raw)
In-Reply-To: <E1pTbcD-00086L-EL@fencepost.gnu.org> (message from Richard Stallman on Sat, 18 Feb 2023 23:47:57 -0500)

> From: Richard Stallman <rms@gnu.org>
> Cc: theophilusx@gmail.com, emacs-devel@gnu.org
> Date: Sat, 18 Feb 2023 23:47:57 -0500
> 
>   > The whole process takes a non-trivial amount of work.  It is described
>   > in make-tarball.txt.  If someone wants to do it, they are welcome.
> 
> The steps all need to be done, but what makes them nontrivial is that
> normally some of them will run into snags that require nontrivial
> corrections.
> 
> Maybe it would be good to do this in a Shell buffer and save the
> typescript, so a more experienced persion can verify it was done
> right.

That's not the main aspect that makes this nontrivial.  Many steps
described in make-tarball.txt require that a human eyeballs the
results of some commands and/or messages from some commands, and fixes
any problems that need fixing.  The process of examining and the
decision which ones are "worth fixing" is what takes time and effort,
and logging what was done in one case makes the next one no easier.

Another non-trivial part is updating the manuals on the Web site.  The
procedure we use for building the manuals is very fragile and tends to
break with every new Texinfo release.

Anyway, this is all moot point now, since Stefan Kangas already did
the job (for which I thank him again).



  reply	other threads:[~2023-02-19  7:05 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
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 [this message]
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=83edqmxhhx.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    --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).