public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Andreas Jaeger <aj@suse.com>
Cc: Mike Frysinger <vapier@gentoo.org>, <libc-alpha@sourceware.org>,
	David Holsgrove <david.holsgrove@xilinx.com>,
	<libc-ports@sourceware.org>,
	John Williams <john.williams@xilinx.com>,
	"Edgar E. Iglesias"	<edgar.iglesias@gmail.com>,
	Vinod Kathail <vinod.kathail@xilinx.com>,
	Tom Shui <tom.shui@xilinx.com>,
	Vidhumouli Hunsigida	<vidhumouli.hunsigida@xilinx.com>,
	Nagaraju Mekala	<nagaraju.mekala@xilinx.com>
Subject: Re: [PATCH 2/3 elf] Add MicroBlaze support to elf.h
Date: Thu, 29 Nov 2012 16:06:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64.1211291605080.21521@digraph.polyomino.org.uk> (raw)
In-Reply-To: <50B71717.1090100@suse.com>

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.

-- 
Joseph S. Myers
joseph@codesourcery.com

  parent reply	other threads:[~2012-11-29 16:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-29  5:29 David Holsgrove
2012-11-29  6:04 ` [PATCH] Adding MicroBlaze support to elf/elf.h David Holsgrove
2012-11-29  7:16 ` [PATCH 2/3 elf] Add MicroBlaze support to elf.h Andreas Jaeger
2012-11-29  7:58   ` Mike Frysinger
2012-11-29  8:04     ` Andreas Jaeger
2012-11-29  8:23       ` David Holsgrove
2012-11-29 16:06       ` Joseph S. Myers [this message]
2012-11-29 16:11         ` Carlos O'Donell
2012-11-29 16:20           ` Joseph S. Myers
2012-11-29  8:03   ` David Holsgrove

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=Pine.LNX.4.64.1211291605080.21521@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=aj@suse.com \
    --cc=david.holsgrove@xilinx.com \
    --cc=edgar.iglesias@gmail.com \
    --cc=john.williams@xilinx.com \
    --cc=libc-alpha@sourceware.org \
    --cc=libc-ports@sourceware.org \
    --cc=nagaraju.mekala@xilinx.com \
    --cc=tom.shui@xilinx.com \
    --cc=vapier@gentoo.org \
    --cc=vidhumouli.hunsigida@xilinx.com \
    --cc=vinod.kathail@xilinx.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).