From: "Kaz Kylheku (libffi)" <382-725-6798@kylheku.com>
To: Ian Lance Taylor <iant@golang.org>
Cc: Ulderico Cirello <uldericofilho@gmail.com>,
"Maciej W. Rozycki" <macro@wdc.com>,
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 18:50:00 -0000 [thread overview]
Message-ID: <3aa631555b402d833aeeb045555ad685@mail.kylheku.com> (raw)
In-Reply-To: <CAOyqgcWcsq+apmJTBsKY4U-_JGHk4zdDPwVpxhSh1NyskjKSgg@mail.gmail.com>
On 2019-11-11 10:34, Ian Lance Taylor wrote:
> On Mon, Nov 11, 2019 at 10:31 AM Kaz Kylheku (libffi)
> <382-725-6798@kylheku.com> wrote:
>>
>> On 2019-11-11 10:15, Ulderico Cirello wrote:
>> > Hi Maciej,
>> >
>> > Go's project doesn't take mail patches for changes.
>>
>> Is it that they'd have to read man pages and learn how to use common
>> utilities?
>>
>> Or that nobody has written a "patch in Go" yet?
>
> Please be polite; thanks.
Ah, that would be, "thank you for your bug report and patch".
next prev parent reply other threads:[~2019-11-11 18:50 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 1/4] libatomic/test: Fix " Maciej W. Rozycki
2019-11-11 18:12 ` [PATCH 2/4] libffi/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) [this message]
2019-11-11 18:33 ` Ian Lance Taylor
2019-11-11 18:44 ` Maciej W. Rozycki
2019-11-11 23:16 ` Ian Lance Taylor
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=3aa631555b402d833aeeb045555ad685@mail.kylheku.com \
--to=382-725-6798@kylheku.com \
--cc=golang-dev@googlegroups.com \
--cc=iant@golang.org \
--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).