mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Future plans for uClibc-ng?
Date: Sun, 3 Jan 2016 10:27:52 +0100	[thread overview]
Message-ID: <20160103092750.GA25456@falbala> (raw)
In-Reply-To: <20160102214949.GA1146@localhost.localdomain>


[-- Attachment #1.1: Type: text/plain, Size: 755 bytes --]

Hei hei,

On Sat, Jan 02, 2016 at 10:49:49PM +0100, Ladislav Michl wrote:
> But are there any active uClibc users?

Do you mean in general or specifically with ptxdist? As far as ptxdist
is concerned, we considered it once for a project with very few RAM,
but didn't have time to evaluate it then. So no experience from my
side for ptxdist with uclibc. 

However I use it on a day to day basis on other projects based on
buildroot (namely fli4l).

Greets
Alex

-- 
»With the first link, the chain is forged. The first speech censured, 
the first thought forbidden, the first freedom denied, chains us all 
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601  D1D5 8FBA 7744 CC87 10D0 ***

[-- Attachment #1.2: Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 91 bytes --]

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  parent reply	other threads:[~2016-01-03  9:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-31 20:48 Bryan Hundven
2016-01-02 21:49 ` Ladislav Michl
2016-01-03  2:02   ` Bryan Hundven
2016-01-03  9:27     ` Robert Schwebel
2016-01-03  9:35       ` Bryan Hundven
2016-01-03  9:27   ` Alexander Dahl [this message]
2016-01-03 11:10     ` Ladislav Michl
2016-01-04 14:08       ` Michael Olbrich

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=20160103092750.GA25456@falbala \
    --to=post@lespocky.de \
    --cc=ptxdist@pengutronix.de \
    /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