From: Jeff Law <jeffreyalaw@gmail.com>
To: Qing Zhao <qing.zhao@oracle.com>
Cc: Nick Alcock via Gcc-patches <gcc-patches@gcc.gnu.org>,
John Henning <john.henning@oracle.com>
Subject: Re: [Patch][doc][PR101843]clarification on building gcc and binutils together
Date: Sun, 19 Sep 2021 10:57:48 -0600 [thread overview]
Message-ID: <e64cc2b1-20c5-ec91-197a-bf60ab908955@gmail.com> (raw)
In-Reply-To: <DC53F68C-DED4-4B11-BABC-97DB3020D763@oracle.com>
On 9/9/2021 9:05 AM, Qing Zhao wrote:
> Hi, Jeff,
>
> Sorry for the late reply.
>
> The following is the reply from John Henning and the updated patch based on your suggestions,
> Please take a look and let us know any issue there.
I would strongly recommend removing all the documentation related to
single tree builds. While they were quite useful in the past, setting
up such a tree these days is error prone and discouraged.
Jeff
next prev parent reply other threads:[~2021-09-19 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 22:27 Qing Zhao
2021-08-23 5:45 ` Jeff Law
2021-09-09 15:05 ` Qing Zhao
2021-09-19 16:57 ` Jeff Law [this message]
2021-09-23 11:07 ` John Henning
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=e64cc2b1-20c5-ec91-197a-bf60ab908955@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=john.henning@oracle.com \
--cc=qing.zhao@oracle.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).