From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Changes in the Buildroot autobuilders
Date: Sun, 16 Jun 2013 19:18:06 +0200 [thread overview]
Message-ID: <20130616191806.7b4a899a@skate> (raw)
In-Reply-To: <20130616170305.GI3495@free.fr>
Dear Yann E. MORIN,
On Sun, 16 Jun 2013 19:03:05 +0200, Yann E. MORIN wrote:
> It would be nice if it were also possible to somehow "subscribe" to a
> list of packages and get a mail when any of these packages fails to
> build.
Indeed. Are we also talking about a daily e-mail?
> For example, I'd like to catch errors in the packages I've submitted.
>
> I see two options for this:
> - add a global MAINTAINERS file that list maintainers for each
> actively maintained packages (a bit like the Linux kernel does);
> - add a FOO_MAINTAINER variable to foo.mk (for each maintained 'foo'
> package).
>
> Would that be possible?
Yes that would be possible. For now, I don't have a particularly strong
opinion between the two solutions you proposed. Maybe the second one is
more Buildroot-ish?
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-16 17:18 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 [this message]
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
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=20130616191806.7b4a899a@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