From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Bugs cleanup (input requested)
Date: Mon, 10 Feb 2014 18:53:39 +0100 [thread overview]
Message-ID: <20140210185339.31f327ee@skate> (raw)
In-Reply-To: <CAAXf6LWN9Cz7b=C5ZDBuNwwpAqLaV1kpN206=1NPN_AWQUEsjw@mail.gmail.com>
Dear Thomas De Schampheleire,
On Mon, 10 Feb 2014 18:48:13 +0100, Thomas De Schampheleire wrote:
> > 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.
>
> Main goal would be to visually separate 'add-package-foo' enhancements
> (which are relatively easy to close) from other enhancements.
Simply give them a distinctive title, like:
"package addition: <package name>"
> Finding people to adopt the package patches in enhancement requests is
> similar to finding people to adopt patches from the patchwork cleanup
> actions. The amount of developers attending the buildroot developer
> days this year gives me good hopes to actually get to this, but it may
> take some time.
Indeed. I am however for fairly aggressively closing enhancement
requests for package additions that are not very interesting to active
contributors, and unlikely to find an adopter. Things like
open-vm-tools doesn't seem that useful to me, for example :)
Therefore, I would reply in the bug report, ask for either the original
bug reporter or another contributor to adopt the patch, and if no reply
within 2 weeks, close the bug.
Best regards,
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 17:53 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
2014-02-10 17:48 ` Thomas De Schampheleire
2014-02-10 17:53 ` Thomas Petazzoni [this message]
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=20140210185339.31f327ee@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