public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: Roland McGrath <roland@hack.frob.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: <libc-ports@sourceware.org>,
	   Richard Henderson <rth@redhat.com>,
	   Chris Metcalf <cmetcalf@tilera.com>,
	   Carlos O'Donell <carlos@redhat.com>
Subject: Re: Ordering of ports move to libc
Date: Thu, 30 Jan 2014 21:07:00 -0000	[thread overview]
Message-ID: <20140130210729.AB82974441@topped-with-meat.com> (raw)
In-Reply-To: Joseph S. Myers's message of  Thursday, 30 January 2014 18:29:33 +0000 <Pine.LNX.4.64.1401301814160.7025@digraph.polyomino.org.uk>

A grep suggests that the arm dependencies on alpha are just msgctl.c,
semctl.c, and shmctl.c.  Is that all you found too?

Given the relative activity of the maintenance of the two ports, I think it
makes more sense to reverse the dependency and move arm first.  I also
think it will help for arm specifically to be the first to move just
because you happen to be its maintainer: you are the person who has done
the most to understand and address the issues in doing a move, so you're
the most likely to do it right (perhaps including solving problems you
didn't think of and discuss here beforehand) and set the example for how to
do it with the least hassle.


Thanks,
Roland

  parent reply	other threads:[~2014-01-30 21:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-30 18:29 Joseph S. Myers
2014-01-30 19:42 ` Chris Metcalf
2014-01-30 21:07 ` Roland McGrath [this message]
2014-01-30 21:29   ` Joseph S. Myers
2014-01-30 21:31     ` Roland McGrath
2014-01-31 14:58       ` Richard Henderson

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=20140130210729.AB82974441@topped-with-meat.com \
    --to=roland@hack.frob.com \
    --cc=carlos@redhat.com \
    --cc=cmetcalf@tilera.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-ports@sourceware.org \
    --cc=rth@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).