Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your daily results for 2019-08-18
Date: Wed, 28 Aug 2019 14:37:50 +0200	[thread overview]
Message-ID: <20190828143750.0948e4ef@windsurf.home> (raw)
In-Reply-To: <20190819124959.quvccga35p2ggkrf@sapphire.tkos.co.il>

Hello,

On Mon, 19 Aug 2019 15:49:59 +0300
Baruch Siach <baruch@tkos.co.il> wrote:

> The list of packages versions in Buildroot seems to be take from the master 
> branch. All these packages were updated in the next branch. I think that when 
> the next branch is active (i.e. has commits not in master), the script should 
> look there instead of master.

I have modified the logic. Now pkg-stats is run with the data from the
next branch when it exists, otherwise using the data of the master
branch. So we simply need to drop the next branch from the official Git
repo when a release is done to have pkg-stats be back in using data
from the master branch.

I have not re-generated the pkg-stats data, so it will have an effect
only tomorrow.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2019-08-28 12:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190819054333.566812D8079@tinkie.tkos.co.il>
2019-08-19 12:49 ` [Buildroot] [autobuild.buildroot.net] Your daily results for 2019-08-18 Baruch Siach
2019-08-19 12:55   ` Thomas Petazzoni
2019-08-19 21:28     ` Arnout Vandecappelle
2019-08-19 21:32       ` Thomas Petazzoni
2019-08-19 22:00         ` Peter Korsgaard
2019-08-20 19:10           ` Arnout Vandecappelle
2019-08-20 19:18             ` Arnout Vandecappelle
2019-08-21  7:51               ` Yann E. MORIN
2019-08-21  8:01                 ` Peter Korsgaard
2019-08-21  9:13                   ` Yann E. MORIN
2019-08-21 10:03                     ` Peter Korsgaard
2019-08-21 20:58                       ` Arnout Vandecappelle
2019-08-26  7:38                       ` Thomas Petazzoni
2019-08-27 20:17                         ` Peter Korsgaard
2019-08-28 12:37   ` Thomas Petazzoni [this message]
     [not found] <5d5a3ea8.1c69fb81.80346.bed9SMTPIN_ADDED_MISSING@mx.google.com>
     [not found] ` <CAFtSRGAfbahUOhw2FEZ5mD1F0s3NpN1kmW5PxkHmPr83yhrxyg@mail.gmail.com>
2019-08-19 12:03   ` Thomas Petazzoni

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=20190828143750.0948e4ef@windsurf.home \
    --to=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox