public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [ANN] U-Boot v2021.01-rc1 released
Date: Thu, 29 Oct 2020 11:36:35 -0400	[thread overview]
Message-ID: <20201029153635.GL5340@bill-the-cat> (raw)
In-Reply-To: <f4e93def-b8c6-7288-949b-3b572e168f94@monstr.eu>

On Thu, Oct 29, 2020 at 04:29:09PM +0100, Michal Simek wrote:
> Hi Tom,
> 
> On 29. 10. 20 15:38, Tom Rini wrote:
> > Hey all,
> > 
> > Well.  I tagged this release on Wednesday.  I drafted this email,
> > uploaded everything, ran the script to update patchwork...
> 
> What does this script do?

Good question!  I took the upstream patchwork post-receive hook example
and tweaked it to instead be a script I call with first/last commits.
What it does is for each commit it calls the internal patchwork tool to
get the hash, and then asks patchwork for the patch ID that matches the
hash.  If found, it then marks that commit as accepted and sets what the
git commit hash for it is.

Note that the biggest issue with this method is that any tweaks done
between posting to patchwork and the actual commit can change the hash,
so we can have stuff accepted but not marked as such, if custodians
don't update this themselves.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20201029/f44a3d04/attachment.sig>

      reply	other threads:[~2020-10-29 15:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-29 14:38 [ANN] U-Boot v2021.01-rc1 released Tom Rini
2020-10-29 15:29 ` Michal Simek
2020-10-29 15:36   ` Tom Rini [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=20201029153635.GL5340@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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