All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/3] support/scripts/pkg-stats: use aiohttp for latest version retrieval
Date: Fri, 28 Aug 2020 17:52:47 +0200	[thread overview]
Message-ID: <87k0xiwywg.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20200808180826.1007656-2-thomas.petazzoni@bootlin.com> (Thomas Petazzoni's message of "Sat, 8 Aug 2020 20:08:23 +0200")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:

 > This commit reworks the code that retrieves the latest upstream
 > version of each package from release-monitoring.org using the aiohttp
 > module. This makes the implementation much more elegant, and avoids
 > the problematic multiprocessing Pool which is causing issues in some
 > situations.

 > Since we're now using some async functionality, the script is Python
 > 3.x only, so the shebang is changed to make this clear.

 > Suggested-by: Titouan Christophe <titouan.christophe@railnova.eu>
 > Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>

Committed to 2020.02.x and 2020.05.x, thanks.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2020-08-28 15:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-08 18:08 [Buildroot] [PATCH v3 0/3] Use aiohttp in pkg-stats Thomas Petazzoni
2020-08-08 18:08 ` [Buildroot] [PATCH v3 1/3] support/scripts/pkg-stats: use aiohttp for latest version retrieval Thomas Petazzoni
2020-08-28 15:52   ` Peter Korsgaard [this message]
2020-08-08 18:08 ` [Buildroot] [PATCH v3 2/3] support/scripts/pkg-stats: use aiohttp for upstream URL checking Thomas Petazzoni
2020-08-28 15:52   ` Peter Korsgaard
2020-08-08 18:08 ` [Buildroot] [PATCH v3 3/3] support/scripts/pkg-stats: show progress of upstream URL and latest version Thomas Petazzoni
2020-08-28 15:52   ` Peter Korsgaard
2020-08-11 20:33 ` [Buildroot] [PATCH v3 0/3] Use aiohttp in pkg-stats Thomas Petazzoni
2020-08-28 15:52 ` Peter Korsgaard

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=87k0xiwywg.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.