From: Mike Stump <mikestump@comcast.net>
To: Kirill Yukhin <kirill.yukhin@gmail.com>
Cc: Richard Henderson <rth@redhat.com>,
Jakub Jelinek <jakub@redhat.com>,
gcc-patches List <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, RFC] Dumping expanded MD files
Date: Fri, 23 Nov 2012 09:26:00 -0000 [thread overview]
Message-ID: <44314D32-9C75-43B7-A7D2-8B3EE052A977@comcast.net> (raw)
In-Reply-To: <CAGs3RfvHEekrCcagF3uvFgsOfW+xLzFyi+RyoEY+qNkNa=-k3w@mail.gmail.com>
On Nov 22, 2012, at 9:48 AM, Kirill Yukhin <kirill.yukhin@gmail.com> wrote:
> This patch adds an utility for dumping MD-files after iterators and
> define_substs expanding.
> What do you guys think?
Cool. (That's not an official review. :-))
next prev parent reply other threads:[~2012-11-23 9:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-22 17:49 Kirill Yukhin
2012-11-23 9:26 ` Mike Stump [this message]
2012-11-24 3:00 ` Hans-Peter Nilsson
2012-11-27 17:34 ` Richard Henderson
2012-11-29 7:22 ` Michael Zolotukhin
2012-11-29 18:41 ` Richard Henderson
2012-11-29 19:06 ` Richard Henderson
2012-11-30 9:10 ` Michael Zolotukhin
2012-11-30 19:13 ` Richard Henderson
2012-12-04 12:59 ` Kirill Yukhin
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=44314D32-9C75-43B7-A7D2-8B3EE052A977@comcast.net \
--to=mikestump@comcast.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=kirill.yukhin@gmail.com \
--cc=rth@redhat.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.
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).