From: Eli Zaretskii <eliz@gnu.org>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: 39546@debbugs.gnu.org, larsi@gnus.org, michael.albinus@gmx.de,
tsdh@gnu.org
Subject: bug#39546: 28.0.50; Do not require subr-x at run time
Date: Fri, 14 Feb 2020 12:16:26 +0200 [thread overview]
Message-ID: <8336bdpj7p.fsf@gnu.org> (raw)
In-Reply-To: <87a75qyx7e.fsf@gmail.com> (message from Tino Calancha on Mon, 10 Feb 2020 22:00:21 +0100)
> From: Tino Calancha <tino.calancha@gmail.com>
> Cc: 39546@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>,
> michael.albinus@gmx.de, larsi@gnus.org
> Date: Mon, 10 Feb 2020 22:00:21 +0100
>
> Tino Calancha <tino.calancha@gmail.com> writes:
>
> >> I have run the testsuite without surprises.
> > Well, actually there was a surprise, but who don't like surprises after
> > all!
> Well, I must recognize I am one of those guys who doesn't like
> surprises. It seems `when-let' became very popular these days.
>
> Here is the updated patch. It takes in account all usages of `when-let'
> once dropped the cookie.
Thanks.
Are we talking about doing these changes on master? Because I think
such wide-sweeping changes that aren't bugfixes are not really
appropriate for the release branch. If you want to move
replace-region-contents to replace.el on emacs-27, I agree, but all
the rest should go to master, I think.
next prev parent reply other threads:[~2020-02-14 10:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 13:59 bug#39546: 28.0.50; Do not require subr-x at run time Tino Calancha
2020-02-10 14:54 ` Michael Albinus
2020-02-10 17:35 ` Tino Calancha
2020-02-10 15:31 ` Eli Zaretskii
2020-02-10 17:26 ` Tino Calancha
2020-02-10 17:39 ` Eli Zaretskii
2020-02-10 19:19 ` Tassilo Horn
2020-02-10 19:59 ` Eli Zaretskii
2020-02-10 20:17 ` Tassilo Horn
2020-02-10 19:30 ` Tino Calancha
2020-02-10 19:54 ` Tassilo Horn
2020-02-10 20:34 ` Tino Calancha
2020-02-10 20:49 ` Tino Calancha
2020-02-10 21:00 ` Tino Calancha
2020-02-14 10:16 ` Eli Zaretskii [this message]
2020-02-19 13:41 ` Lars Ingebrigtsen
2020-08-08 14:06 ` Lars Ingebrigtsen
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=8336bdpj7p.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=39546@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=michael.albinus@gmx.de \
--cc=tino.calancha@gmail.com \
--cc=tsdh@gnu.org \
/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).