From: Eli Zaretskii <eliz@gnu.org>
To: Mark Kennedy <mark.t.kennedy@gmail.com>
Cc: 51794-done@debbugs.gnu.org
Subject: bug#51794: 29.0.50; invalid input events generated from a mouse click for the tab bar
Date: Sun, 21 Nov 2021 17:00:07 +0200 [thread overview]
Message-ID: <83tug5r1u0.fsf@gnu.org> (raw)
In-Reply-To: <CANru7VHoFQwhHcoMCZQ0PeXodYrHKYdS_nQg4y=T_QZaysjorw@mail.gmail.com> (message from Mark Kennedy on Sun, 21 Nov 2021 09:56:47 -0500)
> From: Mark Kennedy <mark.t.kennedy@gmail.com>
> Date: Sun, 21 Nov 2021 09:56:47 -0500
> Cc: Eli Zaretskii <eliz@gnu.org>, 51794-done@debbugs.gnu.org
>
> quick question only indirectly related to the fix. why would it go
> into the emacs-28 branch and not the HEAD branch? if you're busy,
> don't worry about answering. or both branches?
The release branch gets merged to master quite regularly, so this is
not a problem, and the bonus is that the same commit exists on master
as well.
next prev parent reply other threads:[~2021-11-21 15:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 20:49 bug#51794: 29.0.50; invalid input events generated from a mouse click for the tab bar Mark Kennedy
2021-11-13 7:18 ` Eli Zaretskii
[not found] ` <CANru7VHKtNYZBwVHFEt-=25j7PGWkawdU+PWcdAPqdNaKSYP3w@mail.gmail.com>
2021-11-13 13:43 ` Eli Zaretskii
[not found] ` <CANru7VH29KdLB0-Bc-JoDB3x+_-M9irADdQ2=JVkupbLyW15DQ@mail.gmail.com>
2021-11-13 14:40 ` Eli Zaretskii
2021-11-13 14:52 ` Mark Kennedy
2021-11-13 15:29 ` Eli Zaretskii
2021-11-13 15:43 ` Mark Kennedy
2021-11-18 23:39 ` Mark Kennedy
2021-11-19 7:01 ` Eli Zaretskii
2021-11-19 7:54 ` Eli Zaretskii
2021-11-19 9:26 ` martin rudalics
2021-11-19 13:18 ` Mark Kennedy
2021-11-20 8:03 ` Eli Zaretskii
2021-11-20 8:48 ` martin rudalics
2021-11-20 9:07 ` Eli Zaretskii
2021-11-20 9:56 ` martin rudalics
2021-11-20 10:08 ` Eli Zaretskii
2021-11-21 9:12 ` martin rudalics
2021-11-21 14:56 ` Mark Kennedy
2021-11-21 15:00 ` Eli Zaretskii [this message]
2021-11-21 15:20 ` Mark Kennedy
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=83tug5r1u0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=51794-done@debbugs.gnu.org \
--cc=mark.t.kennedy@gmail.com \
/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).