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: Mon, 19 Aug 2019 14:03:53 +0200	[thread overview]
Message-ID: <20190819140353.2cf2c8ee@windsurf.home> (raw)
In-Reply-To: <CAFtSRGAfbahUOhw2FEZ5mD1F0s3NpN1kmW5PxkHmPr83yhrxyg@mail.gmail.com>

Hello Adrien,

+Buildroot mailing list in Cc.

On Mon, 19 Aug 2019 12:35:19 +0200
Adrien Gallou?t <adrien@gallouet.fr> wrote:

> > This is the list of packages for which a new version has been detected
> > and for which you are a registered developer. Please help us improving
> > the quality of Buildroot by bumping these packages to their latest
> > version. Thanks!
> >
> >              name              | found by |        link to
> > release-monitoring.org        |   version    |   upstream
> >
> > -------------------------------+----------+----------------------------------------------+--------------+--------------
> >                           bird |  GUESS   |
> > https://release-monitoring.org/project/00192 | 2.0.4        | 2.0.5
> >
> > --
> > http://autobuild.buildroot.net  
> 
> 
> This is very nice to have this kind of automatic alerts. Well done ;)

Glad to hear you're find those automatic notifications useful. This was
all done by Victor Huesca (in Cc) as part of his internship at Bootlin
this summer, working on Buildroot topics.

> I was aware of this release and tested it the first day and I had lot of
> issue with it, I expect a bugfix release.
> Do you prefer to be syncd everytime?

It is up to you as a developer/maintainer of this package to decide
when it is appropriate to update the version. If you know 2.0.5 has a
number of issues that will be fixed in future releases, you can
perfectly wait until those releases become available. You will only
receive this notification e-mail once a week in the mean time, which I
believe is reasonable.

Thanks!

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

       reply	other threads:[~2019-08-19 12:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5d5a3ea8.1c69fb81.80346.bed9SMTPIN_ADDED_MISSING@mx.google.com>
     [not found] ` <CAFtSRGAfbahUOhw2FEZ5mD1F0s3NpN1kmW5PxkHmPr83yhrxyg@mail.gmail.com>
2019-08-19 12:03   ` Thomas Petazzoni [this message]
     [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

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=20190819140353.2cf2c8ee@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