From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ola: mark as broken
Date: Fri, 28 Apr 2017 23:07:59 +0200 [thread overview]
Message-ID: <20170428230759.64d4427c@free-electrons.com> (raw)
In-Reply-To: <939b0c39-d10b-c699-8367-41f7e57cd4fe@mind.be>
Hello,
On Fri, 28 Apr 2017 21:53:18 +0200, Arnout Vandecappelle wrote:
> We kind of decided a few months ago not use BROKEN anymore, except if we expect
> that it will be repaired again very soon. The idea was that any BROKEN thing
> would be converted into removal with legacy handling at time of release. Do we
> expect the issue to be fixed by then?
>
> If not (probably not), I believe the proper approach is to remove, with legacy
> handling. If the issue gets fixed somewhere down the line, the removal can be
> reverted again.
>
> Make sure the help text of the legacy symbol clearly describes the problem, so
> that anyone who actually needs the package can try to fix it.
I think we can leave this as BROKEN, and shortly before the release
really remove it if upstream has not fixed it.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-04-28 21:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 14:07 [Buildroot] [PATCH] ola: mark as broken Baruch Siach
2017-04-28 19:53 ` Arnout Vandecappelle
2017-04-28 21:07 ` Thomas Petazzoni [this message]
2017-04-29 11:58 ` Thomas Petazzoni
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=20170428230759.64d4427c@free-electrons.com \
--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