unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: 53618@debbugs.gnu.org
Cc: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#53618: 29.0.50; macroexp-warn-and-return incompatible change
Date: Sat, 12 Feb 2022 07:50:39 +0100	[thread overview]
Message-ID: <87fsoo60jk.fsf@gnus.org> (raw)
In-Reply-To: <jwvtud514to.fsf-monnier+emacs@gnu.org> (Stefan Monnier via's message of "Fri, 11 Feb 2022 16:24:37 -0500")

Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of
text editors" <bug-gnu-emacs@gnu.org> writes:

> So I'd appreciate a decision from the maintainers:
>
> Should we keep the backward-incompatible code we currently have on
> `master` or should we take my patch with its someone annoyingly
> placed extra argument (or some yet distinct option)?

We can't break compatibility in this way, so please go ahead and push
your patch.

(A longer term solution would be to introduce a new function with a less
confusing signature, and make the old one obsolete.)

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2022-02-12  6:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-29  0:37 bug#53618: 29.0.50; macroexp-warn-and-return incompatible change Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-29 11:28 ` Alan Mackenzie
2022-01-29 14:46   ` Lars Ingebrigtsen
2022-01-29 15:02     ` Alan Mackenzie
2022-02-11 21:24     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-12  6:50       ` Lars Ingebrigtsen [this message]
2022-02-19 19:20         ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=87fsoo60jk.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=53618@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).