From: Ian Lance Taylor <iant@golang.org>
To: "Maciej W. Rozycki" <macro@wdc.com>
Cc: Ulderico Cirello <uldericofilho@gmail.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
libffi-discuss@sourceware.org,
golang-dev <golang-dev@googlegroups.com>
Subject: Re: [golang-dev] [PATCH 0/4] Fix library testsuite compilation for build sysroot
Date: Mon, 11 Nov 2019 23:16:00 -0000 [thread overview]
Message-ID: <CAOyqgcXHLnNqAnu9g68Q3cjZDkL0d+gGjww9LUCQjWyYOnwbAg@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.21.1911111839170.13542@redsun52.ssa.fujisawa.hgst.com>
On Mon, Nov 11, 2019 at 10:44 AM Maciej W. Rozycki <macro@wdc.com> wrote:
>
> On Mon, 11 Nov 2019, Ian Lance Taylor wrote:
>
> > > Go's project doesn't take mail patches for changes. Please use gerrit ( https://go-review.googlesource.com/ ).
> >
> > These patches are for gccgo, not the gc toolchain. They should
> > probably have been sent to gofrontend-dev rather than golang-dev. The
> > gccgo repo does take patches via e-mail; I route them through Gerrit
> > as needed.
>
> I may have misinterpreted this paragraph[1]:
>
> "Submitting Changes
>
> Changes to the Go frontend should follow the same process as for the
> main Go repository, only for the gofrontend project and the
> gofrontend-dev@googlegroups.com mailing list rather than the go project
> and the golang-dev@googlegroups.com mailing list. Those changes will
> then be merged into the GCC sources."
>
> Sorry about that; I think it might benefit from a rewrite for clarity
> though.
>
> References:
>
> [1] "Contributing to the gccgo frontend - The Go Programming Language",
> <https://golang.org/doc/gccgo_contribute.html>
The paragraph seems reasonable clear to me, so I'm obviously missing
something. Can you suggest a clearer rewrite? Thanks.
Ian
next prev parent reply other threads:[~2019-11-11 23:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 18:12 Maciej W. Rozycki
2019-11-11 18:12 ` [PATCH 2/4] libffi/test: Fix " Maciej W. Rozycki
2019-11-11 18:12 ` [PATCH 1/4] libatomic/test: " Maciej W. Rozycki
2019-11-11 18:15 ` [golang-dev] [PATCH 0/4] Fix library testsuite " Ulderico Cirello
2019-11-11 18:23 ` Kaz Kylheku (libffi)
2019-11-11 18:35 ` Ian Lance Taylor
2019-11-11 18:50 ` Kaz Kylheku (libffi)
2019-11-11 18:33 ` Ian Lance Taylor
2019-11-11 18:44 ` Maciej W. Rozycki
2019-11-11 23:16 ` Ian Lance Taylor [this message]
2019-11-11 18:42 ` Maciej W. Rozycki
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=CAOyqgcXHLnNqAnu9g68Q3cjZDkL0d+gGjww9LUCQjWyYOnwbAg@mail.gmail.com \
--to=iant@golang.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=golang-dev@googlegroups.com \
--cc=libffi-discuss@sourceware.org \
--cc=macro@wdc.com \
--cc=uldericofilho@gmail.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).