From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Andreas Jaeger <aj@suse.com>
Cc: "libc-ports@sourceware.org" <libc-ports@sourceware.org>,
<msalter@redhat.com>
Subject: Re: How to handle patches for it AM33?
Date: Sun, 10 Mar 2013 15:28:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1303101525380.29302@digraph.polyomino.org.uk> (raw)
In-Reply-To: <513CA010.9000200@suse.com>
On Sun, 10 Mar 2013, Andreas Jaeger wrote:
> I have posted a patch for AM33 and nobody reviewed it - it seems we do not
> have a maintainer.
>
> Will someobdy else step up and review this, should I ignore am33 - or just
> commit it?
My view is just commit if you have a patch. We've been waiting since I
reviewed the update patch
<http://sourceware.org/ml/libc-ports/2012-06/msg00066.html> for a revised
version that takes account of my review (and of course of all the global
changes in libc since then that require corresponding port changes).
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2013-03-10 15:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-10 15:00 Andreas Jaeger
2013-03-10 15:28 ` Joseph S. Myers [this message]
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.1303101525380.29302@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=aj@suse.com \
--cc=libc-ports@sourceware.org \
--cc=msalter@redhat.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).