From: "Mattias Engdegård" <mattiase@acm.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Regexp scan of Emacs (April 19)
Date: Fri, 19 Apr 2019 22:29:23 +0200 [thread overview]
Message-ID: <53735D16-4471-4A88-9F59-16941C9E4306@acm.org> (raw)
In-Reply-To: <031ec3d9-a8ad-e656-b0ac-465ec00a285d@cs.ucla.edu>
19 apr. 2019 kl. 18.04 skrev Paul Eggert <eggert@cs.ucla.edu>:
>
> Thanks, these all look useful to me. I installed the attached patch to
> fix the glitches.
Thank you, that patched seems fine to me. a59c41ee81 (cc-mode.el) has been pushed to complete the set.
The subsumption check will be included in a new xr release then.
prev parent reply other threads:[~2019-04-19 20:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-19 9:39 Regexp scan of Emacs (April 19) Mattias Engdegård
2019-04-19 12:42 ` Michael Albinus
2019-04-19 16:04 ` Paul Eggert
2019-04-19 20:29 ` Mattias Engdegård [this message]
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=53735D16-4471-4A88-9F59-16941C9E4306@acm.org \
--to=mattiase@acm.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@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 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).