From: Chong Yidong <cyd@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Order of associations in compilation-error-regexp-alist-alist
Date: Mon, 24 Sep 2012 15:13:44 +0800 [thread overview]
Message-ID: <87d31bnb9z.fsf@gnu.org> (raw)
In-Reply-To: <837grjkigw.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 24 Sep 2012 09:06:39 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> So moving msft before edg-1 would be an OK solution?
Yes, so long as the regression test tells you that this doesn't break
anything else. You should also update compile-tests--test-regexps-data
and the corresponding line in etc/compilation.txt for the new MSVC
message format.
next prev parent reply other threads:[~2012-09-24 7:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 6:28 Order of associations in compilation-error-regexp-alist-alist Eli Zaretskii
2012-09-24 7:00 ` Chong Yidong
2012-09-24 7:06 ` Eli Zaretskii
2012-09-24 7:13 ` Chong Yidong [this message]
2012-10-14 7:42 ` 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=87d31bnb9z.fsf@gnu.org \
--to=cyd@gnu.org \
--cc=eliz@gnu.org \
--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).