This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH 2/3 elf] Add MicroBlaze support to elf.h
- From: "Carlos O'Donell" <carlos at systemhalted dot org>
- To: "Joseph S. Myers" <joseph at codesourcery dot com>
- Cc: Andreas Jaeger <aj at suse dot com>, Mike Frysinger <vapier at gentoo dot org>, libc-alpha at sourceware dot org, David Holsgrove <david dot holsgrove at xilinx dot com>, libc-ports at sourceware dot org, John Williams <john dot williams at xilinx dot com>, "Edgar E. Iglesias" <edgar dot iglesias at gmail dot com>, Vinod Kathail <vinod dot kathail at xilinx dot com>, Tom Shui <tom dot shui at xilinx dot com>, Vidhumouli Hunsigida <vidhumouli dot hunsigida at xilinx dot com>, Nagaraju Mekala <nagaraju dot mekala at xilinx dot com>
- Date: Thu, 29 Nov 2012 11:11:14 -0500
- Subject: Re: [PATCH 2/3 elf] Add MicroBlaze support to elf.h
- References: <CAM=EW8Y-tqvbZwtewup6UagcgJiHEtDmapEmoiR7ZW0SW_-pCg@mail.gmail.com><50B70BC6.5020502@suse.com><201211290258.36850.vapier@gentoo.org><50B71717.1090100@suse.com><Pine.LNX.4.64.1211291605080.21521@digraph.polyomino.org.uk>
On Thu, Nov 29, 2012 at 11:05 AM, Joseph S. Myers
<joseph@codesourcery.com> wrote:
> On Thu, 29 Nov 2012, Andreas Jaeger wrote:
>
>> David, we've just frozen glibc for development, these kind of patches are too
>> late for glibc 2.17. Please update them and they will get properly reviewed
>> and added once 2.17 is released.
>
> There's no risk of such patches requiring any updates to existing
> architectures, or breaking them, or requiring any updates to message
> translations, so I see no reason for them to be affected by the freeze.
This is the second time we've had this kind of discussion.
However, you did not reply to my comments last time[1].
I will say them again for the record.
There are both direct and indirect benefits here.
The direct benefit is that it's one less patch I have to
review going onto trunk.
The indirect benefit is that we get the community into the
habit and discipline of setting aside trivial changes to
focus on stabilizing trunk.
Does that make sense?
I don't mind if this patch gets checked into trunk, but
please work with David to ensure that it goes in without
error.
Cheers,
Carlos.
[1] http://sourceware.org/ml/libc-alpha/2012-06/msg00267.html