From: Mike Looijmans <mike.looijmans@topic.nl>
To: openembedded-core@lists.openembedded.org
Subject: Re: opkg refactoring
Date: Sun, 08 Feb 2015 17:14:37 +0100 [thread overview]
Message-ID: <54D78B6D.9040900@topic.nl> (raw)
In-Reply-To: <20150207115559.GA7478@crash.betafive.co.uk>
> I didn't realise people were following oe-core master on deployments of a few
> thousand systems! This is definitely a use-case for the stable branches.
In that case I have some interesting information for you. OpenPLi also
follows 'master' (because for many things we need the bleeding edge new
stuff). OpenPLi and its derivatives are being used on millions of settop
boxes. Just the "feed" servers consume about 4 terabytes of traffic each
month.
--
Mike Looijmans
prev parent reply other threads:[~2015-02-08 16:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 22:15 [PATCH V2 0/7] opkg refactoring Paul Barker
2015-01-16 22:15 ` [PATCH V2 1/7] opkg-arch-config: Renamed from opkg-config-base Paul Barker
2015-01-16 22:15 ` [PATCH V2 2/7] opkg-collateral: Simplify source files Paul Barker
2015-01-16 22:15 ` [PATCH V2 3/7] opkg: Merge opkg.inc into recipe and tidy up Paul Barker
2015-01-16 22:15 ` [PATCH V2 4/7] opkg: Merge in opkg-collateral Paul Barker
2015-01-16 22:15 ` [PATCH V2 5/7] poky-feed-config-opkg: Remove Paul Barker
2015-01-16 22:15 ` [PATCH V2 6/7] opkg: Backport improvements to opkg-key Paul Barker
2015-01-16 22:15 ` [PATCH V2 7/7] opkg-keyrings: New recipe Paul Barker
2015-02-11 0:43 ` Richard Tollerton
2015-02-11 8:14 ` Paul Barker
2015-02-11 22:49 ` Richard Tollerton
2015-02-07 10:47 ` opkg refactoring Peter Urbanec
2015-02-07 11:55 ` Paul Barker
2015-02-07 14:10 ` Peter Urbanec
2015-02-08 16:14 ` Mike Looijmans [this message]
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=54D78B6D.9040900@topic.nl \
--to=mike.looijmans@topic.nl \
--cc=openembedded-core@lists.openembedded.org \
/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