From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattias.engdegard@gmail.com>
Cc: 70794@debbugs.gnu.org, spacibba@aol.com
Subject: bug#70794: 30.0.50; Add Rust compilation regex
Date: Mon, 03 Jun 2024 19:33:19 +0300 [thread overview]
Message-ID: <86ikyqkmuo.fsf@gnu.org> (raw)
In-Reply-To: <8BC5E59B-63B1-4784-9454-51925E9DBCFC@gmail.com> (message from Mattias Engdegård on Mon, 3 Jun 2024 18:22:48 +0200)
> From: Mattias Engdegård <mattias.engdegard@gmail.com>
> Date: Mon, 3 Jun 2024 18:22:48 +0200
> Cc: spacibba@aol.com,
> 70794@debbugs.gnu.org
>
> > If you revert it, please fix this ASAP and install the results, since
> > I'd like to have this on the emacs-20 branch, which will be cut
> > soon-ish.
>
> Personally I strongly prefer no rule to a broken one, or even to Mattias's-best-guess-of-what-a-correct-rule-might-look-like.
Fine by me (I don't use Rust), but is the rule really broken? What
happens if you move it to the end?
next prev parent reply other threads:[~2024-06-03 16:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87y18nsp84.fsf.ref@aol.com>
2024-05-06 1:28 ` bug#70794: 30.0.50; Add Rust compilation regex Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-11 8:51 ` Eli Zaretskii
2024-05-15 13:10 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-18 10:52 ` Eli Zaretskii
2024-05-31 17:15 ` Mattias Engdegård
2024-06-03 14:41 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-03 15:35 ` Mattias Engdegård
2024-06-03 14:54 ` Mattias Engdegård
2024-06-03 15:28 ` Eli Zaretskii
2024-06-03 16:22 ` Mattias Engdegård
2024-06-03 16:33 ` Eli Zaretskii [this message]
2024-06-03 16:59 ` Mattias Engdegård
2024-06-04 22:06 ` Stefan Kangas
2024-06-05 22:56 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-06 7:34 ` Stefan Kangas
2024-06-03 22:36 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-04 14:33 ` Eli Zaretskii
2024-06-03 15:30 ` 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=86ikyqkmuo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=70794@debbugs.gnu.org \
--cc=mattias.engdegard@gmail.com \
--cc=spacibba@aol.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).