public inbox for buildbot@sourceware.org
 help / color / mirror / Atom feed
From: Szabolcs Nagy <Szabolcs.Nagy@arm.com>
To: Mark Wielaard <mark@klomp.org>
Cc: buildbot@sourceware.org, Luis Machado <luis.machado@arm.com>,
	Christophe Lyon <christophe.lyon@arm.com>
Subject: Re: [PATCH] Add ARM thanks for new workers
Date: Fri, 8 Jul 2022 13:52:04 +0100	[thread overview]
Message-ID: <YsgodPa9G40nb76W@arm.com> (raw)
In-Reply-To: <20220708123503.34976-1-mark@klomp.org>

The 07/08/2022 14:35, Mark Wielaard wrote:
> ---
>  htdocs/index.html.post | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/htdocs/index.html.post b/htdocs/index.html.post
> index de93f63..74ebcbb 100644
> --- a/htdocs/index.html.post
> +++ b/htdocs/index.html.post
> @@ -11,6 +11,8 @@
>         debian-arm64 and debian-armhf workers</li>
>       <li>Frank Eigler for the fedrawhide-x86_64 worker</li>
>       <li>IBM for the ibm_power8, ibm_power9 and ibm_power10 workers</li>
> +     <li>ARM for the arm64-ubuntu20_04, arm64-ubuntu22_04,
> +            armhf-ubuntu20_04 and armhf-ubuntu22_04 workers</li>


sorry, can you make that

"The Works on Arm initiative for the ..."

(Arm manages the build workers, but the actual machines
are provided by the works on arm initiative and we are
required to credit them where appropriate.)

>        </ul>
>      </p>
>    </body>
> --
> 2.30.2
>
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

  reply	other threads:[~2022-07-08 12:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-08 12:35 Mark Wielaard
2022-07-08 12:52 ` Szabolcs Nagy [this message]
2022-07-08 13:05   ` Mark Wielaard

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=YsgodPa9G40nb76W@arm.com \
    --to=szabolcs.nagy@arm.com \
    --cc=buildbot@sourceware.org \
    --cc=christophe.lyon@arm.com \
    --cc=luis.machado@arm.com \
    --cc=mark@klomp.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).