From: Mark Corbin <mark@dibsco.co.uk>
To: buildroot@busybox.net
Subject: [Buildroot] Autobuilder Package Stats Page
Date: Wed, 04 Dec 2019 15:12:50 +0000 [thread overview]
Message-ID: <2139527.4b9fbVHFrc@laptop> (raw)
In-Reply-To: <20191204155348.39878299@windsurf>
On Wednesday, 4 December 2019 14:53:48 GMT Thomas Petazzoni wrote:
> On Wed, 04 Dec 2019 13:24:52 +0000
>
> Mark Corbin <mark@dibsco.co.uk> wrote:
> > I've been updating package URLs based on the status information shown on
> > the 'package stats' page (http://autobuild.buildroot.org/stats/), but the
> > page output hasn't changed to reflect these new updates.
> >
> > I was wondering when/how the page is updated? I have been checking the
> > current URL status of packages by running './support/scripts/pkg_stats'
> > directly from the command line, but it would be useful if the web page
> > was refreshed regularly to capture any changes.
>
> The page is updated once a day, the last date is at the bottom of the
> page, together with the commit id.
>
> When a "next" branch exists, the page is based on data from the next
> branch, so that we use the latest package versions known by Buildroot.
> However, all your URL-related changes have been merged to master, so
> they didn't show up in the refreshed statistics page.
Do any changes made to 'master' normally get committed to 'next' too when it
exists?
next prev parent reply other threads:[~2019-12-04 15:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 13:24 [Buildroot] Autobuilder Package Stats Page Mark Corbin
2019-12-04 14:53 ` Thomas Petazzoni
2019-12-04 15:07 ` Peter Korsgaard
2019-12-04 15:12 ` Mark Corbin [this message]
2019-12-04 15:18 ` 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=2139527.4b9fbVHFrc@laptop \
--to=mark@dibsco.co.uk \
--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.