From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: robin@terpri.org, 19790@debbugs.gnu.org, larsi@gnus.org,
monnier@iro.umontreal.ca, michael_heerdegen@web.de
Subject: bug#19790: [PATCH] destructive splicing in backquote
Date: Sat, 14 Sep 2019 16:30:04 +0300 [thread overview]
Message-ID: <834l1fypib.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmn0=iyuuV0+==DTygK+TraRMzNgaYUivFXFPSNX+uRvGg@mail.gmail.com> (message from Stefan Kangas on Sat, 14 Sep 2019 14:31:21 +0200)
> From: Stefan Kangas <stefan@marxist.se>
> Date: Sat, 14 Sep 2019 14:31:21 +0200
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, Lars Ingebrigtsen <larsi@gnus.org>,
> Robin Templeton <robin@terpri.org>, 19790@debbugs.gnu.org,
> Michael Heerdegen <michael_heerdegen@web.de>
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > I have no opinion about the change, but I think this should be in
> > NEWS.
>
> Thanks, I have attached a new patch with a suggested NEWS entry.
Looks OK, but I think the entry should be moved to the "Incompatible
changes" part.
Thanks.
next prev parent reply other threads:[~2019-09-14 13:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 6:39 bug#19790: [PATCH] destructive splicing in backquote Robin Templeton
2015-02-06 15:29 ` Stefan Monnier
2015-02-07 18:51 ` Robin Templeton
2015-02-07 21:46 ` Robin Templeton
2015-02-08 19:23 ` Stefan Monnier
2015-02-08 19:38 ` Artur Malabarba
2015-02-09 3:10 ` Stefan Monnier
2015-02-09 13:03 ` Artur Malabarba
2016-02-23 11:08 ` Lars Ingebrigtsen
2019-06-25 17:59 ` Lars Ingebrigtsen
2019-06-25 22:52 ` Michael Heerdegen
2019-09-13 23:59 ` Stefan Kangas
2019-09-14 7:15 ` Eli Zaretskii
2019-09-14 12:31 ` Stefan Kangas
2019-09-14 13:30 ` Eli Zaretskii [this message]
2019-09-15 14:55 ` Stefan Kangas
2019-09-15 1:46 ` Stefan Monnier
2019-09-15 14:57 ` Stefan Kangas
2019-09-26 16:38 ` Stefan Kangas
2019-09-14 12:07 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834l1fypib.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=19790@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=michael_heerdegen@web.de \
--cc=monnier@iro.umontreal.ca \
--cc=robin@terpri.org \
--cc=stefan@marxist.se \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.