From: Mike Frysinger <vapier@gentoo.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 9/9] toolchain: speed up sysroot lib copying
Date: Mon, 10 Oct 2011 11:46:32 -0400 [thread overview]
Message-ID: <201110101146.33586.vapier@gentoo.org> (raw)
In-Reply-To: <20111010172952.77ba7d69@skate>
On Monday 10 October 2011 11:29:52 Thomas Petazzoni wrote:
> Le Mon, 10 Oct 2011 11:22:48 -0400, Mike Frysinger a ?crit :
> > yes & no. it's supposed to be here:
> > http://blackfin.uclinux.org/git/?p=buildroot
> >
> > but it seems they haven't published their internal development tree yet,
> > and i obviously cannot do that for them
>
> Ok, too bad. Is there a way for us to have a contact in this team, so
> we can tell our interest in seeing their developments merged upstream?
uclinux-dist-devel at blackfin.uclinux.org is the general development mailing list
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20111010/5a3c4b41/attachment-0001.asc>
next prev parent reply other threads:[~2011-10-10 15:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-09 17:44 [Buildroot] [pull request v2] Pull request for branch for-2011.11/ext-toolchain-updates Thomas Petazzoni
2011-10-09 17:44 ` [Buildroot] [PATCH 1/9] external toolchain: slightly optimize the copy of the toolchain sysroot Thomas Petazzoni
2011-10-09 22:00 ` Peter Korsgaard
2011-10-10 6:43 ` Thomas Petazzoni
2011-10-10 6:48 ` Thomas Petazzoni
2011-10-10 6:55 ` Peter Korsgaard
2011-10-09 17:44 ` [Buildroot] [PATCH 2/9] toolchain-external: allow specifying extra external libraries Thomas Petazzoni
2011-10-09 17:44 ` [Buildroot] [PATCH 3/9] ext-toolchain: Add CodeSourcery SH uClinux 2011.03 Thomas Petazzoni
2011-10-09 17:44 ` [Buildroot] [PATCH 4/9] ext-toolchain: Bump version of CodeSourcery MIPS 2011.03 Thomas Petazzoni
2011-10-09 17:44 ` [Buildroot] [PATCH 5/9] ext-toolchain: Add CodeSourcery SH GNU/Linux 2011.03 Thomas Petazzoni
2011-10-09 17:44 ` [Buildroot] [PATCH 6/9] ext-toolchain: Add CodeSoucery x86 GNU/Linux 2010.09 Thomas Petazzoni
2011-10-09 17:44 ` [Buildroot] [PATCH 7/9] ext-toolchain: Take into account Mentor Graphics acquisition of CodeSoucery Thomas Petazzoni
2011-10-09 17:44 ` [Buildroot] [PATCH 8/9] external-toolchain: Slightly optimize toolchain extraction Thomas Petazzoni
2011-10-09 21:42 ` Yann E. MORIN
2011-10-10 7:57 ` Peter Korsgaard
2011-10-09 17:44 ` [Buildroot] [PATCH 9/9] toolchain: speed up sysroot lib copying Thomas Petazzoni
2011-10-09 21:46 ` Yann E. MORIN
2011-10-10 2:25 ` Mike Frysinger
2011-10-10 6:44 ` Thomas Petazzoni
2011-10-10 15:12 ` Mike Frysinger
2011-10-10 15:19 ` Thomas Petazzoni
2011-10-10 15:22 ` Mike Frysinger
2011-10-10 15:29 ` Thomas Petazzoni
2011-10-10 15:46 ` Mike Frysinger [this message]
2011-10-10 7:57 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2011-10-02 19:20 [Buildroot] [pull request] Pull request for branch for-2011.11/ext-toolchain-updates Thomas Petazzoni
2011-10-02 19:20 ` [Buildroot] [PATCH 9/9] toolchain: speed up sysroot lib copying Thomas Petazzoni
2011-10-02 22:55 ` Yann E. MORIN
2011-10-04 6:10 ` Arnout Vandecappelle
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=201110101146.33586.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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