From: "Jose E. Marchesi" <jemarch@gnu.org>
To: Mark Wielaard <mark@klomp.org>
Cc: buildbot@sourceware.org, poke-devel@gnu.org
Subject: Re: [PATCH] Add gnupoke snapshot scheduler, factory and builder
Date: Mon, 17 Apr 2023 11:29:31 +0200 [thread overview]
Message-ID: <87cz42q2kk.fsf@gnu.org> (raw)
In-Reply-To: <20230416205048.GF20056@gnu.wildebeest.org> (Mark Wielaard's message of "Sun, 16 Apr 2023 22:50:48 +0200")
Hi Mark.
> On Sun, Apr 16, 2023 at 09:53:34PM +0200, Jose E. Marchesi wrote:
>> This and the Fedora ARM support means I should add new little graphics
>> to http://jemarch.net/poke?
>
> For the fedora arm64 builder you could add:
>
> <a
> href="https://builder.sourceware.org/buildbot/#builders/gnupoke-fedora-arm64"><img
> src="https://builder.sourceware.org/buildbot/badges/gnupoke-fedora-arm64.svg?left_text=%20%20fedora-arm64%20%20"></a>
I just added the above in https://jemarch.net/poke.
> For the snapshots we should see where they exactly land when there is
> a real build. It was supposed to go into "trunk" or "poke-[123]" under
> https://snapshots.sourceware.org/gnupoke/ but the first build didn't
> have a branch associated with it, so it moved a level too high.
>
> Please push a new commit to top of git or one of the maint/poke-*
> branches, so we can check where they end up exactly.
I just pushed a commit to `master'.
next prev parent reply other threads:[~2023-04-17 9:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-16 19:05 Mark Wielaard
2023-04-16 19:53 ` Jose E. Marchesi
2023-04-16 20:50 ` Mark Wielaard
2023-04-17 9:29 ` Jose E. Marchesi [this message]
2023-04-17 10:15 ` 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=87cz42q2kk.fsf@gnu.org \
--to=jemarch@gnu.org \
--cc=buildbot@sourceware.org \
--cc=mark@klomp.org \
--cc=poke-devel@gnu.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).