From: Mark Wielaard <mark@klomp.org>
To: Maxim Kuvyrkov via Overseers <overseers@sourceware.org>
Cc: Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>,
gcc@gcc.gnu.org, libc-alpha <libc-alpha@sourceware.org>,
binutils@sourceware.org, gdb@sourceware.org
Subject: Re: Sourceware @ Conservancy - Year One
Date: Thu, 30 May 2024 12:36:46 +0200 [thread overview]
Message-ID: <20240530103646.GC26515@gnu.wildebeest.org> (raw)
In-Reply-To: <1E2BED27-9721-4729-8785-F6047EE6C646@linaro.org>
Hi Maxim,
On Thu, May 30, 2024 at 12:18:38PM +0400, Maxim Kuvyrkov via Overseers wrote:
> > On May 29, 2024, at 23:02, Mark Wielaard <mark@klomp.org> wrote:
> > And a special thanks to ARM who have been using
> > https://patchwork.sourceware.org/ to provide a pre-commit testing
> > service for various projects.
>
> Thanks for the great update!
>
> Minor nitpick: pre-commit testing for AArch64 and AArch32
> architectures is provided by Linaro Toolchain Working Group (Linaro
> TCWG).
Sorry for getting the credit wrong. Proper credit is important. And in
this case I really should have known. All pre-commit emails start with
[Linaro-TCWG-CI]. I did think about just mentioning the individuals
who made things happen. But then getting individual names wrong is
even worse than getting corporation names wrong...
Thanks Maxim for making the Linaro Toolchain Working Group pre-commit
testing for AArch64 and AArch32 happen!
Cheers,
Mark
prev parent reply other threads:[~2024-05-30 10:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 19:02 Mark Wielaard
2024-05-30 8:18 ` Maxim Kuvyrkov
2024-05-30 10:36 ` Mark Wielaard [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=20240530103646.GC26515@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=libc-alpha@sourceware.org \
--cc=maxim.kuvyrkov@linaro.org \
--cc=overseers@sourceware.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).