From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Bumping packages: some comments/suggestions
Date: Sun, 13 Oct 2013 17:06:24 +0200 [thread overview]
Message-ID: <20131013170624.43960a83@skate> (raw)
In-Reply-To: <CAAXf6LXQ4Tv3QGsx2atT=C6yg-HDGoRHDKpJBKyzC4g8-phbDw@mail.gmail.com>
Dear Thomas De Schampheleire,
On Sun, 13 Oct 2013 17:01:48 +0200, Thomas De Schampheleire wrote:
> > Any opinion about this? I believe it would make more sense to invest
> > time doing this than doing many many bumps on all packages.
>
> I assume you're only talking about a way to automatically _detect_
> that there are new versions of a given package, and the actual update
> in buildroot is still done manually, right?
Of course. But this way, we would have some kind of "dashboard" showing
us which packages might benefit from a bump.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-13 15:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-13 9:42 [Buildroot] Bumping packages: some comments/suggestions Thomas Petazzoni
2013-10-13 10:44 ` Axel Lin
2013-10-13 13:42 ` Thomas Petazzoni
2013-10-13 15:01 ` Thomas De Schampheleire
2013-10-13 15:06 ` Thomas Petazzoni [this message]
2013-10-13 21:04 ` Jerzy Grzegorek
2013-10-14 7:09 ` Thomas Petazzoni
2013-10-14 7:40 ` Jeremy Rosen
2013-10-14 9:30 ` Thomas Petazzoni
2013-10-14 9:38 ` Jeremy Rosen
2013-10-14 10:02 ` Thomas De Schampheleire
2013-10-14 10:04 ` Thomas Petazzoni
2013-10-14 12:58 ` arnaud aujon
2013-10-14 13:56 ` Thomas Petazzoni
2013-10-14 17:11 ` arnaud aujon
2013-10-14 21:55 ` Arnout Vandecappelle
2013-10-15 7:34 ` Thomas Petazzoni
2013-10-15 19:55 ` Arnout Vandecappelle
2013-10-14 13:45 ` rjbarnet at rockwellcollins.com
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=20131013170624.43960a83@skate \
--to=thomas.petazzoni@free-electrons.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