public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: Matt Turner <mattst88@gmail.com>
To: "Carlos O'Donell" <carlos@codesourcery.com>
Cc: libc-ports@sourceware.org,
	"Joseph S. Myers" <joseph@codesourcery.com>,
		"Ryan S. Arnold" <rsa@us.ibm.com>,
	Andreas Schwab <schwab@linux-m68k.org>,
		Richard Henderson <rth@twiddle.net>, Andreas Jaeger <aj@suse.de>,
	Philip Blundell <philb@gnu.org>
Subject: Re: Glibc-ports status? Creating glibc-ports tarball for 2.13?
Date: Mon, 14 Feb 2011 14:52:00 -0000	[thread overview]
Message-ID: <AANLkTikC_yt=nW-D+7rNvBOahV3RFmCcBrp3MS53CBQW@mail.gmail.com> (raw)
In-Reply-To: <4D59305D.7040605@codesourcery.com>

On Mon, Feb 14, 2011 at 1:38 PM, Carlos O'Donell
<carlos@codesourcery.com> wrote:
> What is the status of all the machines in glibc-ports with respect to
> the glibc-2.13 tag in libc-ports?
>
> Alpha - Richard?

Needs a couple header-updating patches, but otherwise only trivial
changes. I'd be nice to get these into glibc-2.13, but it won't really
hurt anything if they don't get in.

It sure would be nice if we could avoid patching nearly identical
headers in nearly identical ways for each architecture...

Matt

  parent reply	other threads:[~2011-02-14 14:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-14 13:40 Carlos O'Donell
2011-02-14 13:55 ` Andreas Jaeger
2011-02-14 14:07 ` Ryan Arnold
2011-02-14 14:52 ` Matt Turner [this message]
2011-02-14 15:58   ` Carlos O'Donell
2011-02-18 15:35     ` Guy Martin
2011-02-18 18:57       ` Roland McGrath
2011-02-14 17:36 ` Andreas Schwab
2011-02-14 18:37 ` Joseph S. Myers

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='AANLkTikC_yt=nW-D+7rNvBOahV3RFmCcBrp3MS53CBQW@mail.gmail.com' \
    --to=mattst88@gmail.com \
    --cc=aj@suse.de \
    --cc=carlos@codesourcery.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-ports@sourceware.org \
    --cc=philb@gnu.org \
    --cc=rsa@us.ibm.com \
    --cc=rth@twiddle.net \
    --cc=schwab@linux-m68k.org \
    /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).