From: "João Távora" <joaotavora@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: johnw@gnu.org, emacs-devel <emacs-devel@gnu.org>
Subject: Re: Very annoying Flymake regression in Emacs 26.1
Date: Sat, 12 May 2018 11:41:07 +0100 [thread overview]
Message-ID: <CALDnm53+6Cd=PMtxPrdOecLXZA0cOOys6daE-J2SM_opppunuQ@mail.gmail.com> (raw)
In-Reply-To: <83k1s9md5k.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]
Done, it's 934bb475b9a729d0be4d78cd89c1d22d032ee3d7 in
emacs-26 (which I hope is the "release branch" you're talking of
, if it isn't please let me know).
In master I will later address the cause of the error, which is a bug in
itself, but this needn't make it to the release branch.
João
On Sat, May 12, 2018 at 10:33 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > From: João Távora <joaotavora@gmail.com>
> > Cc: emacs-devel@gnu.org, johnw@gnu.org
> > Date: Sat, 12 May 2018 10:01:43 +0100
> >
> > > If it isn't rare, I wonder how come no one noticed until now that we
> > > are littering the filesystem with these
> >
> > Good question! I guess few people are using it, or they're using it
> > with special care, or they are used to the _flymake.c garbage
> > anyway because the old flymake used to make it from time to time (though
> > not in such a trivial case)
>
> OK, please cherry-pick the commit you made to master to the release
> branch.
>
> Thanks.
>
--
João Távora
[-- Attachment #2: Type: text/html, Size: 1803 bytes --]
next prev parent reply other threads:[~2018-05-12 10:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-11 21:35 Very annoying Flymake regression in Emacs 26.1 João Távora
2018-05-12 7:08 ` Eli Zaretskii
2018-05-12 9:01 ` João Távora
2018-05-12 9:33 ` Eli Zaretskii
2018-05-12 10:41 ` João Távora [this message]
2018-05-12 10:45 ` Eli Zaretskii
2018-05-13 5:03 ` John Wiegley
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='CALDnm53+6Cd=PMtxPrdOecLXZA0cOOys6daE-J2SM_opppunuQ@mail.gmail.com' \
--to=joaotavora@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=johnw@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.