From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Changes in the Buildroot autobuilders
Date: Tue, 18 Jun 2013 09:12:39 +0200 [thread overview]
Message-ID: <20130618091239.28d1dbc8@skate> (raw)
In-Reply-To: <E6BF041E97966E4DB955F0DF883AD2D633A03317@de02wembxa.internal.synopsys.com>
Dear Mischa Jonker,
On Mon, 17 Jun 2013 20:09:51 +0000, Mischa Jonker wrote:
> How would we handle architecture-specific failures for a package if we don't have a global MAINTAINERS file? Add another _MAINTAINER variable in the config.in.<arch> file?
I believe architecture-specific failures would have to be handled
separately. We can't really add a maintainer into a Config.in file.
Even if we have a global MAINTAINERS file, how would architecture
maintainers be expressed? In the kernel, the MAINTAINERS file creates a
relation between a person and set of files/directories, but an
architecture in Buildroot is not a set of files or directories.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-06-18 7:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-16 16:00 [Buildroot] Changes in the Buildroot autobuilders Thomas Petazzoni
2013-06-16 17:03 ` Yann E. MORIN
2013-06-16 17:18 ` Thomas Petazzoni
2013-06-16 17:25 ` Yann E. MORIN
2013-06-16 18:05 ` Thomas Petazzoni
2013-06-17 7:45 ` Maxime Ripard
2013-06-17 7:49 ` Thomas Petazzoni
2013-06-17 16:20 ` Spenser Gilliland
2013-06-17 17:54 ` Yann E. MORIN
2013-06-17 18:07 ` ANDY KENNEDY
2013-06-17 20:09 ` Mischa Jonker
2013-06-18 7:12 ` Thomas Petazzoni [this message]
2013-06-17 20:39 ` Spenser Gilliland
2013-06-18 6:21 ` Arnout Vandecappelle
2013-06-18 7:16 ` Thomas Petazzoni
2013-06-18 16:46 ` Yann E. MORIN
2013-06-17 6:25 ` Arnout Vandecappelle
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=20130618091239.28d1dbc8@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 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.