From: "João Távora" <joaotavora@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gerd.moellmann@gmail.com, Spencer Baugh <sbaugh@janestreet.com>,
sbaugh@catern.com, me@eshelyaron.com, 69809@debbugs.gnu.org
Subject: bug#69809: 30.0.50; flymake: error in process sentinel
Date: Thu, 25 Jul 2024 08:45:12 +0100 [thread overview]
Message-ID: <CALDnm50Fd=KQXES_OZmOKnCi4FCzSzLFLuTG_gwy_8047Kgd1A@mail.gmail.com> (raw)
In-Reply-To: <86ikwu53rr.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 971 bytes --]
On Thu, Jul 25, 2024 at 8:28 AM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Spencer Baugh <sbaugh@janestreet.com>
> > Cc: Eshel Yaron <me@eshelyaron.com>, gerd.moellmann@gmail.com, Eli
> > Zaretskii <eliz@gnu.org>, 69809@debbugs.gnu.org, sbaugh@catern.com
> > Date: Wed, 24 Jul 2024 12:25:00 -0400
> >
> > > Spencer please have a look and push it if you agree.
> >
> > Yes, this seems good to me, thank you for the improved patch!
> >
> > I unfortunately don't have commit access, so perhaps someone else can
> > install the patch.
>
> I tried installing the last patch posted by João, but it failed to
> apply, even with the -3 option and with options that ignore whitespace
> changes.
>
> João, please either install this on the emacs-30 branch or post an
> updated patch that will apply cleanly.
>
I posted two patches (as attached .patch files) Maybe that's the issue.
Not 100% what patches Spencer has tested or greenlighting.
[-- Attachment #2: Type: text/html, Size: 1713 bytes --]
next prev parent reply other threads:[~2024-07-25 7:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 7:09 bug#69809: 30.0.50; flymake: error in process sentinel Gerd Möllmann
2024-03-21 10:23 ` Eli Zaretskii
2024-03-23 14:02 ` sbaugh
2024-03-23 14:20 ` Gerd Möllmann
2024-07-11 9:45 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-11 11:15 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-11 11:46 ` Gerd Möllmann
2024-07-12 6:27 ` Eli Zaretskii
2024-07-16 20:48 ` Spencer Baugh
2024-07-17 6:12 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-17 8:20 ` João Távora
2024-07-17 9:07 ` João Távora
2024-07-17 13:08 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-17 13:44 ` João Távora
2024-07-17 17:25 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-17 17:38 ` João Távora
2024-07-17 23:54 ` João Távora
2024-07-18 0:10 ` João Távora
2024-07-24 16:25 ` Spencer Baugh
2024-07-25 7:28 ` Eli Zaretskii
2024-07-25 7:45 ` João Távora [this message]
2024-07-25 10:50 ` Eli Zaretskii
2024-07-25 11:49 ` João Távora
2024-07-27 7:26 ` 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
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='CALDnm50Fd=KQXES_OZmOKnCi4FCzSzLFLuTG_gwy_8047Kgd1A@mail.gmail.com' \
--to=joaotavora@gmail.com \
--cc=69809@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=gerd.moellmann@gmail.com \
--cc=me@eshelyaron.com \
--cc=sbaugh@catern.com \
--cc=sbaugh@janestreet.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).