From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Mark Wielaard <mark@klomp.org>, Mark Wielaard <mjw@gnu.org>
Cc: libc-alpha@sourceware.org, DJ Delorie <dj@redhat.com>,
Carlos O'Donell <carlos@redhat.com>
Subject: Re: patchwork upgrade week
Date: Thu, 23 Jun 2022 14:09:53 +0530 [thread overview]
Message-ID: <9e158b8a-05e7-8e9a-f57b-ba6850ba51d4@gotplt.org> (raw)
In-Reply-To: <e54d09a3fc21813771a7b938bcc68f70b06eda0c.camel@klomp.org>
On 23/06/2022 13:25, Mark Wielaard wrote:
> OK, so that would work like the git try branches, but tells the
> buildbot to also find the same patch on patchwork to add a check
> result?
>
> Could we then use patchwork/hasher.py to calculate the hash of the
> commit and look it up in the project patch list so it can be update it
> with the builder check result?
Yes, as long as the diff is identical, hasher.py should be able to find it.
Sid
next prev parent reply other threads:[~2022-06-23 8:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 10:26 Siddhesh Poyarekar
2022-06-22 6:53 ` Siddhesh Poyarekar
2022-06-22 21:27 ` Mark Wielaard
2022-06-23 2:16 ` Siddhesh Poyarekar
2022-06-23 7:55 ` Mark Wielaard
2022-06-23 8:39 ` Siddhesh Poyarekar [this message]
2022-06-27 17:23 ` DJ Delorie
2022-07-01 11:04 ` Mark Wielaard
2022-07-01 21:01 ` DJ Delorie
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=9e158b8a-05e7-8e9a-f57b-ba6850ba51d4@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=carlos@redhat.com \
--cc=dj@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=mark@klomp.org \
--cc=mjw@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).