From: Ian Lance Taylor <iant@golang.org>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
Ian Lance Taylor via Gcc-patches <gcc-patches@gcc.gnu.org>,
gofrontend-dev <gofrontend-dev@googlegroups.com>
Subject: Re: Go patch committed: Accept -fgo-embedcfg option
Date: Tue, 5 Jan 2021 11:49:18 -0800 [thread overview]
Message-ID: <CAKOQZ8zw5st4hXOVgZDct2pyNQV7SSWwstNXdg2njCVvQTrZpw@mail.gmail.com> (raw)
In-Reply-To: <20210105151504.GP725145@tucnak>
On Tue, Jan 5, 2021 at 7:15 AM Jakub Jelinek via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
> On Tue, Jan 05, 2021 at 11:06:27AM +0100, Andreas Schwab wrote:
> > FAIL: compiler driver --help=go option(s): "^ +-.*[^:.]$" absent from output: " -fgo-embedcfg=<file> List embedded files via go:embed"
>
> Fixed thusly, committed as obvious.
>
> 2021-01-05 Jakub Jelinek <jakub@redhat.com>
>
> * lang.opt (fgo-embedcfg=): Add full stop at the end of description.
Thanks.
Ian
prev parent reply other threads:[~2021-01-05 19:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 1:41 Ian Lance Taylor
2021-01-05 10:06 ` Andreas Schwab
2021-01-05 15:15 ` Jakub Jelinek
2021-01-05 19:49 ` Ian Lance Taylor [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=CAKOQZ8zw5st4hXOVgZDct2pyNQV7SSWwstNXdg2njCVvQTrZpw@mail.gmail.com \
--to=iant@golang.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gofrontend-dev@googlegroups.com \
--cc=jakub@redhat.com \
--cc=schwab@linux-m68k.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).