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] Build results for 2018-03-26
Date: Tue, 27 Mar 2018 09:47:54 +0200	[thread overview]
Message-ID: <20180327094754.35db48d1@windsurf.home> (raw)
In-Reply-To: <87in9it123.fsf@dell.be.48ers.dk>

Hello,

On Tue, 27 Mar 2018 09:44:36 +0200, Peter Korsgaard wrote:

>  > Arnout, Peter, any preference ? I'm leaning towards (2) since that's
>  > the solution that doesn't pollute Buildroot with unnecessary stuff.  
> 
> I agree. It does mean that we need all autobuilders to update, but that
> shouldn't be a big problem.

It also means that if someone uses autobuild-run to test another branch
than 2018.02.x, master or next, we have no idea whether we should use
"dependencies" or "core-dependencies".

But well, I believe autobuild-run is kind of an internal tool, it's not
really meant to be used as a generic tool. If people do this, then it's
up to them to figure out how to tweak it.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-03-27  7:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-27  6:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-03-26 Thomas Petazzoni
2018-03-27  6:45 ` Baruch Siach
2018-03-27  7:15   ` Thomas Petazzoni
2018-03-27  7:44     ` Peter Korsgaard
2018-03-27  7:47       ` Thomas Petazzoni [this message]
2018-03-27  8:00         ` 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=20180327094754.35db48d1@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