From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: contovob@tcd.ie, michael.albinus@gmx.de, emacs-devel@gnu.org
Subject: Re: master 5b962a7: Avoid double argument evaluation in vc-call macro
Date: Tue, 21 Sep 2021 17:20:24 +0300 [thread overview]
Message-ID: <83lf3qxb6f.fsf@gnu.org> (raw)
In-Reply-To: <fe46e5c9-9902-4553-3e51-526aa154cb84@yandex.ru> (message from Dmitry Gutov on Tue, 21 Sep 2021 16:52:43 +0300)
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Tue, 21 Sep 2021 16:52:43 +0300
> Cc: emacs-devel@gnu.org
>
> On 21.09.2021 16:45, Basil L. Contovounesios wrote:
> > Lars argued that the "buggy" behaviour was explicitly documented for a
> > long time, so it's safer to announce it:https://bugs.gnu.org/50690#8
> >
> > I was happy to oblige to tickle my megalomania and because I'm just a
> > poor student who can't afford to be sued.
>
> I think the NEWS entry could be useful for someone who comes later and
> writes code which needs to be compatible with previous versions of
> Emacs: if double evaluation is a problem for them, they could at least
> find the NEWS entry, to see when it was fixed.
>
> We don't usually do that for bug fixes, but since this was the
> documented behavior... *shrug*
Yes, it's borderline, so I see no harm in having that in NEWS.
next prev parent reply other threads:[~2021-09-21 14:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210921115002.28282.50636@vcs0.savannah.gnu.org>
[not found] ` <20210921115004.44D90200AF@vcs0.savannah.gnu.org>
2021-09-21 12:51 ` master 5b962a7: Avoid double argument evaluation in vc-call macro Michael Albinus
2021-09-21 13:40 ` Po Lu
2021-09-21 16:51 ` Basil L. Contovounesios
2021-09-21 13:45 ` Basil L. Contovounesios
2021-09-21 13:52 ` Dmitry Gutov
2021-09-21 14:20 ` Eli Zaretskii [this message]
2021-09-21 14:10 ` Michael Albinus
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=83lf3qxb6f.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=contovob@tcd.ie \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
/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).