From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] uclibc: clean-up test suite build command
Date: Mon, 20 Apr 2015 08:39:07 +0000 [thread overview]
Message-ID: <1429519146.2756.2.camel@synopsys.com> (raw)
In-Reply-To: <20150325173919.0b2d0528@free-electrons.com>
Hi Thomas,
On Wed, 2015-03-25 at 17:39 +0100, Thomas Petazzoni wrote:
> Dear Alexey Brodkin,
>
> On Wed, 25 Mar 2015 07:49:24 +0000, Alexey Brodkin wrote:
>
> > > Unfortunately, unless this cleaned-up version brings significant
> > > benefits, I believe the best option is to keep things as is until AVR32
> > > support is really deprecated and removed from Buildroot, so that we can
> > > drop support for 0.9.31.
> >
> > Now when AVR32 support is finally dropped do you think this patch might
> > be accepted?
>
> Yes, sure! AVR32 / supporting old uClibc versions was the only reason
> to keep the old way around. Now that AVR32 is gone, all clean-ups we
> can do following this removal are very welcome.
Please treat this as a gentle reminder. I'm wondering if that pretty
straight-forward change has a chance for being applied?
From your previous answer I understood that you\re in general fine with
clean-up stuff like that.
-Alexey
next prev parent reply other threads:[~2015-04-20 8:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 17:26 [Buildroot] [PATCH] uclibc: clean-up test suite build command Alexey Brodkin
2014-06-30 18:07 ` Thomas Petazzoni
2014-07-01 10:27 ` Alexey Brodkin
2015-03-25 7:49 ` Alexey Brodkin
2015-03-25 16:39 ` Thomas Petazzoni
2015-04-20 8:39 ` Alexey Brodkin [this message]
2015-04-20 8:58 ` Thomas Petazzoni
2015-04-20 9:10 ` Alexey Brodkin
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=1429519146.2756.2.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