From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Bugs cleanup (input requested)
Date: Mon, 10 Feb 2014 17:48:58 +0100 [thread overview]
Message-ID: <20140210174858.62e72709@skate> (raw)
In-Reply-To: <CAAXf6LWzDBwN=U=7U9yK7oQPhq2+c=C6ZHmrK_kiy-3hOAu2BA@mail.gmail.com>
Dear Thomas De Schampheleire,
On Mon, 10 Feb 2014 16:20:10 +0100, Thomas De Schampheleire wrote:
> > For these bug reports, did you change them to another state?
>
> Not yet. I see that several already are in state 'enhancement', prio P5.
>
> What about additionally 'assigning' them to a mailing address that
> reflects that these are packages? Currently unassigned bugs are
> assigned to 'unassigned at buildroot.uclibc.org'. Is this a real e-mail
> address or not? What about we assign 'new package' entries to
> 'unassigned-newpkg at buildroot.uclibc.org' instead?
What would this be useful for? I believe we should either find people
willing to "adopt" those packages and do the remaining work needed to
get them merge, or close the bugs.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-02-10 16:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 10:21 [Buildroot] Bugs cleanup (input requested) Thomas De Schampheleire
2014-02-10 12:02 ` Maxime Hadjinlian
2014-02-10 15:10 ` Thomas De Schampheleire
2014-02-10 14:21 ` Danomi Manchego
2014-02-10 14:43 ` Thomas Petazzoni
2014-02-10 15:12 ` Thomas De Schampheleire
2014-02-10 15:20 ` Thomas De Schampheleire
2014-02-10 16:48 ` Thomas Petazzoni [this message]
2014-02-10 17:48 ` Thomas De Schampheleire
2014-02-10 17:53 ` Thomas Petazzoni
2014-02-10 20:39 ` Arnout Vandecappelle
2014-02-11 20:52 ` Thomas De Schampheleire
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=20140210174858.62e72709@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