unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: lux <lx@shellcodes.org>
To: Eli Zaretskii <eliz@gnu.org>, Stefan Kangas <stefankangas@gmail.com>
Cc: 61595@debbugs.gnu.org
Subject: bug#61595: [PATCH] 28.3; test/lisp/emacs-lisp/copyright-tests.el: Fix test failure.
Date: Sat, 18 Feb 2023 17:33:19 +0800	[thread overview]
Message-ID: <tencent_DA338E3510350D77E3F29CE17CC18A9CCF08@qq.com> (raw)
In-Reply-To: <83k00fz5wx.fsf@gnu.org>

On Sat, 2023-02-18 at 11:20 +0200, Eli Zaretskii wrote:
> > From: Stefan Kangas <stefankangas@gmail.com>
> > Date: Sat, 18 Feb 2023 01:10:57 -0800
> > Cc: 61595@debbugs.gnu.org
> > 
> > I don't think we will need to worry about test failures on the
> > emacs-28
> > branch.  The purpose of tests is to aid during development, and
> > there
> > will be no more development on that branch.  I also think it's
> > better to
> > minimize the amount of changes on very old branches.
> 
> Agreed.  On top of that, this release being an emergency security
> fix,
> it should IMO have only the minimum number of changes strictly
> necessary to fix the particular problem for which it is being
> released.
> 
> 
> 

Okay, I understand. Thank you.





  reply	other threads:[~2023-02-18  9:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-18  5:46 bug#61595: [PATCH] 28.3; test/lisp/emacs-lisp/copyright-tests.el: Fix test failure Xi Lu
2023-02-18  7:29 ` Eli Zaretskii
2023-02-18  7:38   ` lux
2023-02-18  7:49     ` Eli Zaretskii
2023-02-18  7:58       ` lux
2023-02-18  9:10         ` Stefan Kangas
2023-02-18  9:20           ` Eli Zaretskii
2023-02-18  9:33             ` lux [this message]
2023-02-18  9:51               ` Stefan Kangas

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_DA338E3510350D77E3F29CE17CC18A9CCF08@qq.com \
    --to=lx@shellcodes.org \
    --cc=61595@debbugs.gnu.org \
    --cc=eliz@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).