From: Jeff Law <jeffreyalaw@gmail.com>
To: Jivan Hakobyan <jivanhakobyan9@gmail.com>, gcc-patches@gcc.gnu.org
Cc: Jeff Law <jlaw@ventanamicro.com>
Subject: Re: [wwwdocs] Broken URL to README.Portability
Date: Sat, 17 Jun 2023 12:02:32 -0600 [thread overview]
Message-ID: <fa7078bc-48c2-6b16-e200-6284b0d4686a@gmail.com> (raw)
In-Reply-To: <CAHso6sM7+ke8AFqD4nv6otqopKNVtap-uMmxjdrkC7CA_HLYvg@mail.gmail.com>
On 6/14/23 06:06, Jivan Hakobyan via Gcc-patches wrote:
> This patch fixes the link to README.Portability in "GCC Coding Conventions"
> page
Thanks. I've pushed this to the htdocs repo.
jeff
prev parent reply other threads:[~2023-06-17 18:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 12:06 Jivan Hakobyan
2023-06-17 18:02 ` Jeff Law [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=fa7078bc-48c2-6b16-e200-6284b0d4686a@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jivanhakobyan9@gmail.com \
--cc=jlaw@ventanamicro.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).