Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Changes in the Buildroot autobuilders
Date: Sun, 16 Jun 2013 19:25:08 +0200	[thread overview]
Message-ID: <20130616172508.GL3495@free.fr> (raw)
In-Reply-To: <20130616191806.7b4a899a@skate>

On 2013-06-16 19:18 +0200, Thomas Petazzoni spake thusly:
> 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?

If there are build failures, yes.
Of course, no need for a mail if no build failure.

> > 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?

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

I would not expect more than one maintainer, but then why restrict
ourselves...

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

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2013-06-16 17:25 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 [this message]
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=20130616172508.GL3495@free.fr \
    --to=yann.morin.1998@free.fr \
    --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