Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Changes in the Buildroot autobuilders
Date: Sun, 16 Jun 2013 20:05:40 +0200	[thread overview]
Message-ID: <20130616200540.5a370504@skate> (raw)
In-Reply-To: <20130616172508.GL3495@free.fr>

Dear Yann E. MORIN,

On Sun, 16 Jun 2013 19:25:08 +0200, Yann E. MORIN wrote:

> > Indeed. Are we also talking about a daily e-mail?
> 
> If there are build failures, yes.
> Of course, no need for a mail if no build failure.

Ok. This will require a little bit of work, because until now, the
autobuild.buildroot.org machine, which sends the daily e-mails, was not
using the Buildroot source code at all to do its job. So either the
slave build machines will have to submit the list of maintainers of the
failing package as part of the tarball they submit to
autobuild.buildroot.org, or autobuild.b.o will have to look at the
Buildroot source code to find the maintainers of the failing package.

Either way, it will not be immediate to implement.

> Yes, that's my preferred one.
> 
> Should that be a single email adress, or can this be a list?
>     FOO_MAINTAINERS = me at there him at overthere somone at somewhere

A list of e-mails, definitely.

> I'll adapt the manual to document this new variable, and will submit a
> patch to add myself as maintainer for a few packages.

Ok.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-06-16 18:05 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 [this message]
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=20130616200540.5a370504@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