From: Stephan Hoffmann <sho@relinux.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Microblaze: Improvements in the build system
Date: Tue, 01 May 2012 16:13:39 +0200 [thread overview]
Message-ID: <4F9FEF93.4020609@relinux.de> (raw)
In-Reply-To: <201204281817.16635.arnout@mind.be>
Am 28.04.2012 18:17, schrieb Arnout Vandecappelle:
> Even though I made a lot of comments here, it definitely looks like
> an improvement!
>
> Regards,
> Arnout
>
Thanks for your constructive comments. I will see when I have time to
implement them. But that isn't much likely in time for the upcoming
2012.05 release;-(
Kind regards
Stephan
--
reLinux - Stephan Hoffmann
Am Schmidtgrund 124 50765 K?ln
Tel. +49.221.95595-19 Fax: -64
www.reLinux.de sho at reLinux.de
next prev parent reply other threads:[~2012-05-01 14:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 16:18 [Buildroot] [PATCH] Microblaze: Improvements in the build system Stephan Hoffmann
2012-04-28 16:17 ` Arnout Vandecappelle
2012-05-01 14:13 ` Stephan Hoffmann [this message]
2012-05-01 14:52 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2012-04-08 16:47 Stephan Hoffmann
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=4F9FEF93.4020609@relinux.de \
--to=sho@relinux.de \
--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