From: Roland McGrath <roland@hack.frob.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: <libc-alpha@sourceware.org>, <libc-ports@sourceware.org>
Subject: Re: e500 port plans
Date: Wed, 25 Sep 2013 21:44:00 -0000 [thread overview]
Message-ID: <20130925214435.DB8D92C07C@topped-with-meat.com> (raw)
In-Reply-To: Joseph S. Myers's message of Wednesday, 25 September 2013 21:30:41 +0000 <Pine.LNX.4.64.1309252129590.31429@digraph.polyomino.org.uk>
> The two changes (e500 port, and moving powerpc bits out of ports/) seem
> completely independent to me.
They are. But we need to get the ball rolling on migrating things out of
ports somehow, and adding more things into ports/ does not help. Migrating
the powerpc bits out of ports/ seems far simpler than the other cases there
(because it's not the whole port that is in ports/, but just a few pieces).
I suspect it's not much more than just actually moving the files.
prev parent reply other threads:[~2013-09-25 21:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 23:28 Joseph S. Myers
2013-09-24 23:01 ` Roland McGrath
2013-09-25 21:30 ` Joseph S. Myers
2013-09-25 21:44 ` Roland McGrath [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=20130925214435.DB8D92C07C@topped-with-meat.com \
--to=roland@hack.frob.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=libc-ports@sourceware.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).