From: Hongxu Jia <hongxu.jia@windriver.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: <jakub@gcc.gnu.org>, <rguenth@gcc.gnu.org>,
<gcc-patches@gcc.gnu.org>,
<richard.purdie@linuxfoundation.org>
Subject: Re: [PATCH V3]PR other/70268: map one directory name (old) to another (new) in __FILE__
Date: Wed, 23 Mar 2016 07:49:00 -0000 [thread overview]
Message-ID: <56F23F75.8090204@windriver.com> (raw)
In-Reply-To: <56EB8F3E.90901@windriver.com>
Ping, is that OK? Any suggestions?
//Hongxu
On 03/18/2016 01:16 PM, Hongxu Jia wrote:
> Changed in V3:
>
> - Rebase to latest master (efc86c4c627b82364f118a29b5d9d58cad8b8c76)
>
> - Fix bad formatting (missing space before '(').
>
> - Use of @code{} around literal source code text.
>
> //Hongxu
>
prev parent reply other threads:[~2016-03-23 7:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 8:57 [PATCH]PR " Hongxu Jia
2016-03-17 9:54 ` [PATCH V2]PR " Hongxu Jia
2016-03-17 22:47 ` [PATCH]PR " Joseph Myers
2016-03-18 2:30 ` Hongxu Jia
2016-03-18 7:56 ` [PATCH V3]PR " Hongxu Jia
2016-03-18 8:05 ` Bernhard Reutner-Fischer
2016-03-18 8:11 ` Hongxu Jia
2016-03-18 9:36 ` Hongxu Jia
2016-03-23 7:49 ` Hongxu Jia [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56F23F75.8090204@windriver.com \
--to=hongxu.jia@windriver.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=rguenth@gcc.gnu.org \
--cc=richard.purdie@linuxfoundation.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.
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).