From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] uClibc-ng 1.0.6 update
Date: Mon, 24 Aug 2015 15:36:14 +0000 [thread overview]
Message-ID: <1440430574.2745.13.camel@synopsys.com> (raw)
Hi Waldemar,
I noticed that you recently cut release of 1.0.6 uclibc-ng.
I'm wondering if you plan to submit a patch to Buildroot with bumping
of uClibc version?
I may do it myself but just to escape duplicates IMHO would
be good to check with you.
-Alexey
next reply other threads:[~2015-08-24 15:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 15:36 Alexey Brodkin [this message]
[not found] ` <BCD08FBE-D0D8-4720-A851-F66BB2D256BE@waldemar-brodkorb.de>
2015-08-24 21:00 ` [Buildroot] uClibc-ng 1.0.6 update Alexey Brodkin
2015-08-24 21:06 ` Thomas Petazzoni
2015-08-25 8:36 ` Waldemar Brodkorb
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=1440430574.2745.13.camel@synopsys.com \
--to=alexey.brodkin@synopsys.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