all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "kassick@gmail.com" <kassick@gmail.com>
To: Andrea Corallo <acorallo@gnu.org>
Cc: 71654-done@debbugs.gnu.org
Subject: bug#71654: [PATCH] Fix display-buffer-override-next-command
Date: Wed, 19 Jun 2024 19:16:13 -0300	[thread overview]
Message-ID: <CAJvJD8joCrCOWLPEuQgZSy3NehbJ1m47Ej5dT+k8-nyW0shkDQ@mail.gmail.com> (raw)
In-Reply-To: <yp1sex8fur4.fsf@fencepost.gnu.org>

[-- Attachment #1: Type: text/plain, Size: 722 bytes --]

Ah, time for me to update here, then!

Anyone having this issue in 29 or older could just use advice to patch the
function and move on, don't see any reason to backport it.



Em qua., 19 de jun. de 2024 às 19:11, Andrea Corallo <acorallo@gnu.org>
escreveu:

> "kassick@gmail.com" <kassick@gmail.com> writes:
>
> > Awesome!
> >
> > Any chance of cherry-picking it on emacs-29?
>
> We could do that if we feel sure this has no implications, but there
> will be no more emacs 29 releases anyway and we are about to branch 30,
> so I'm not sure it's worth of even if the change looks simple.
>
>   Andrea
>


-- 
Rodrigo Virote Kassick
------------------------------------------------------------

[-- Attachment #2: Type: text/html, Size: 1353 bytes --]

  reply	other threads:[~2024-06-19 22:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-19 15:20 bug#71654: [PATCH] Fix display-buffer-override-next-command kassick
2024-06-19 21:17 ` Jeremy Bryant via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-19 21:53   ` kassick
2024-06-19 21:32 ` Andrea Corallo
2024-06-19 21:54   ` kassick
2024-06-19 22:11     ` Andrea Corallo
2024-06-19 22:16       ` kassick [this message]
2024-06-20  7:55         ` Andrea Corallo
2024-06-20  5:15       ` Eli Zaretskii

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=CAJvJD8joCrCOWLPEuQgZSy3NehbJ1m47Ej5dT+k8-nyW0shkDQ@mail.gmail.com \
    --to=kassick@gmail.com \
    --cc=71654-done@debbugs.gnu.org \
    --cc=acorallo@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 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.