mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Bryan Hundven <bryanhundven@gmail.com>
To: ptxdist@pengutronix.de
Cc: Waldemar Brodkorb <wbx@openadk.org>
Subject: [ptxdist] Future plans for uClibc-ng?
Date: Thu, 31 Dec 2015 12:48:31 -0800	[thread overview]
Message-ID: <20151231204831.GA28276@hp2000d> (raw)


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

Hello,

I'm curious to know if ptxdist/OSELAS.Toolchain plans to support
uClibc-ng in the future?

http://www.uclibc-ng.org/

Cheers,

-Bryan

Happy New Year!

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

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

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

             reply	other threads:[~2015-12-31 20:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-31 20:48 Bryan Hundven [this message]
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
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=20151231204831.GA28276@hp2000d \
    --to=bryanhundven@gmail.com \
    --cc=ptxdist@pengutronix.de \
    --cc=wbx@openadk.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