From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Changes in the Buildroot autobuilders
Date: Tue, 18 Jun 2013 18:46:48 +0200 [thread overview]
Message-ID: <20130618164648.GA3952@free.fr> (raw)
In-Reply-To: <20130618091639.4f82fa41@skate>
Thomas, All,
On 2013-06-18 09:16 +0200, Thomas Petazzoni spake thusly:
> On Tue, 18 Jun 2013 08:21:17 +0200, Arnout Vandecappelle wrote:
> > So I think a nice solution would be to add a script in support/scripts
> > that explicitly encodes all the maintainers - maintainers can add
> > themselves with patches (just like in the kernel). The a.b.o would fetch
> > the script once a day just before sending out its daily mails, and call
> > it with everything it knows about the build failure set in the environment.
>
> This does sound like a nice idea, but I would like it to also handle
> architecture maintainers if possible.
>
> So something like:
>
> support/script/get_maintainer --arch arc --package tvheadend
>
> would return:
>
> Mischa Jonker <Mischa.Jonker@synopsys.com>
> 'Yann E. MORIN' <yann.morin.1998@free.fr>
>
> the first being the architecture maintainer, the second being the
> package maintainer.
OK, I'll code this, then.
> But then, I would probably have to send one e-mail per failure, because
> grouping them would be hard since there may be another failure for
> tvheadend, but not on the ARC architecture.
Maybe you'd want to separate the mails:
- one for packages
- one for achitectures
> > However, Spenser points out in another mail:
> >
> > > I think many people would like to know if something they did may have
> > > triggered a bug, not just the maintainer of the package.
> >
> > I could agree with sending mails automatically to the authors of a
> > package commit if the commit was done in the last week or so.
>
> Hum, ok. Not impossible to do, for sure.
Yes, sounds like a good idea.
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. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2013-06-18 16:46 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
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 [this message]
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=20130618164648.GA3952@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