From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 14/25] lua-bit32: new package
Date: Sat, 18 Mar 2017 11:42:09 +0100 [thread overview]
Message-ID: <20170318114209.123e1ea8@free-electrons.com> (raw)
In-Reply-To: <04a224aa-c599-d927-79ad-869dcd7d9f7c@mind.be>
Hello,
On Fri, 17 Mar 2017 23:17:25 +0100, Arnout Vandecappelle wrote:
> I wouldn't say "regularly". I do look occasionally. I would pay a lot more
> attention if I got an occasional personal mail.
OK. But it probably wouldn't be "occasional". From a quick look, we
have currently ~500 packages not associated to a developer, so about
1/4 of all packages we have.
But currently, we indeed don't notice when there is a build failure on
a package that is orphaned. Having at least you notified on orphaned
packages build failures would raise the attention on this or that
package being orphaned, and then we can see what needs to be done: find
if someone has been active on that package recently and is willing to
adopt it, remove the package if it's too broken and nobody cares, etc.
What do you think?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-03-18 10:42 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 17:00 [Buildroot] [PATCH for-next 0/25] Lua(Rocks) improvements Arnout Vandecappelle
2017-02-23 17:00 ` [Buildroot] [PATCH 01/25] lutok: move to Lua libraries menu Arnout Vandecappelle
2017-03-02 21:29 ` Thomas Petazzoni
2017-02-23 17:00 ` [Buildroot] [PATCH 02/25] cosmo: remove broken package Arnout Vandecappelle
2017-03-02 21:31 ` Thomas Petazzoni
2017-02-23 17:00 ` [Buildroot] [PATCH 03/25] luarocks-package: use $(HOST_PKG_VERSION) instead of $(PKG_VERSION) Arnout Vandecappelle
2017-03-02 21:43 ` Thomas Petazzoni
2017-02-23 17:00 ` [Buildroot] [PATCH 04/25] manual: luarocks: improve tutorial example Arnout Vandecappelle
2017-03-02 21:43 ` Thomas Petazzoni
2017-02-23 17:00 ` [Buildroot] [PATCH 05/25] lpty: remove LPTY_VERSION_UPSTREAM Arnout Vandecappelle
2017-03-02 21:45 ` Thomas Petazzoni
2017-02-23 17:00 ` [Buildroot] [PATCH 06/25] lua-periphery: remove LUA_PERIPHERY_VERSION_UPSTREAM Arnout Vandecappelle
2017-03-02 21:45 ` Thomas Petazzoni
2017-02-23 17:00 ` [Buildroot] [PATCH 07/25] luasec: remove LUASEC_VERSION_UPSTREAM Arnout Vandecappelle
2017-03-02 21:45 ` Thomas Petazzoni
2017-02-23 17:00 ` [Buildroot] [PATCH 08/25] ljlinenoise: remove default definition of PKG_SUBDIR Arnout Vandecappelle
2017-03-02 21:48 ` Thomas Petazzoni
2017-02-23 17:00 ` [Buildroot] [PATCH 09/25] lua-csnappy: " Arnout Vandecappelle
2017-02-23 17:00 ` [Buildroot] [PATCH 10/25] lua-iconv: " Arnout Vandecappelle
2017-02-23 17:00 ` [Buildroot] [PATCH 11/25] luacrypto: " Arnout Vandecappelle
2017-02-23 17:00 ` [Buildroot] [PATCH 12/25] lunit: " Arnout Vandecappelle
2017-02-23 17:00 ` [Buildroot] [PATCH 13/25] package/Config.in: explain that lua package names should start with lua Arnout Vandecappelle
2017-03-02 21:50 ` Thomas Petazzoni
2017-03-02 22:19 ` Arnout Vandecappelle
2017-03-02 22:22 ` Thomas Petazzoni
2017-03-02 22:26 ` Arnout Vandecappelle
2017-03-02 22:38 ` Thomas Petazzoni
2017-02-23 17:00 ` [Buildroot] [PATCH 14/25] lua-bit32: new package Arnout Vandecappelle
2017-03-02 21:54 ` Thomas Petazzoni
2017-03-02 22:24 ` Arnout Vandecappelle
2017-03-17 16:14 ` Thomas Petazzoni
2017-03-17 22:17 ` Arnout Vandecappelle
2017-03-18 10:42 ` Thomas Petazzoni [this message]
2017-03-18 13:17 ` Arnout Vandecappelle
2017-03-18 13:49 ` [Buildroot] Orphan package notification Thomas Petazzoni
2017-03-18 14:03 ` Arnout Vandecappelle
2017-02-23 17:00 ` [Buildroot] [PATCH 15/25] luaposix: fix runtime by selecting "bit32" instead of "bitop" Arnout Vandecappelle
2017-03-02 21:58 ` Thomas Petazzoni
2017-03-02 22:25 ` Arnout Vandecappelle
2017-03-02 22:28 ` Thomas Petazzoni
2017-03-02 23:02 ` Arnout Vandecappelle
2017-02-23 17:00 ` [Buildroot] [PATCH 16/25] luarocks-package: rework extraction Arnout Vandecappelle
2017-03-02 22:24 ` Thomas Petazzoni
2017-02-23 17:00 ` [Buildroot] [PATCH 17/25] lua-bit32: remove custom extract commands Arnout Vandecappelle
2017-03-02 22:24 ` Thomas Petazzoni
2017-02-23 17:00 ` [Buildroot] [PATCH 18/25] luarocks-package: introduce PKG_NAME_UPSTREAM Arnout Vandecappelle
2017-03-02 22:26 ` Thomas Petazzoni
2017-02-23 17:00 ` [Buildroot] [PATCH 19/25] lua-bit32: use PKG_NAME_UPSTREAM Arnout Vandecappelle
2017-03-02 22:26 ` Thomas Petazzoni
2017-02-23 17:00 ` [Buildroot] [PATCH 20/25] luarocks-package: lowercase the upstream name for LuaRocks Arnout Vandecappelle
2017-02-23 17:00 ` [Buildroot] [PATCH 21/25] lua-coat: use PKG_NAME_UPSTREAM Arnout Vandecappelle
2017-02-23 17:00 ` [Buildroot] [PATCH 22/25] lua-cjson: use LUA_CJSON_SUBDIR Arnout Vandecappelle
2017-02-23 17:00 ` [Buildroot] [PATCH 23/25] lua-testmore: use PKG_NAME_UPSTREAM Arnout Vandecappelle
2017-02-23 17:00 ` [Buildroot] [PATCH 24/25] luabitop: " Arnout Vandecappelle
2017-02-23 17:00 ` [Buildroot] [PATCH 25/25] lua: remove documentation from target Arnout Vandecappelle
2017-02-24 6:59 ` [Buildroot] [PATCH for-next 0/25] Lua(Rocks) improvements François Perrad
2017-02-24 9:09 ` Arnout Vandecappelle
2017-02-24 10:57 ` François Perrad
2017-03-05 21:05 ` 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=20170318114209.123e1ea8@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