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: Carlos O'Donell <carlos_odonell@mentor.com>,
	   libc-ports@sourceware.org,
	   libc-alpha <libc-alpha@sourceware.org>
Subject: Re: Request for help: Fix building tarballs for ports add-on.
Date: Thu, 14 Jun 2012 16:47:00 -0000	[thread overview]
Message-ID: <20120614164730.CA15D2C0A4@topped-with-meat.com> (raw)
In-Reply-To: Joseph S. Myers's message of  Thursday, 14 June 2012 11:02:30 +0000 <Pine.LNX.4.64.1206141059310.21295@digraph.polyomino.org.uk>

> On Wed, 13 Jun 2012, Roland McGrath wrote:
> 
> > I've been thinking that right after 2.16 will be a good time to consolidate
> > the repositories (just the initial step, making it ports/ under the libc
> > tree).
> 
> We'll need to work out if that comes with any change to expectations 
> regarding what people update in global changes.

I propose that the repository consolidation have no immediate ramifications
other than on the use of one repository rather than two.  Further changes
can be done incrementally and discussed on their own.


Thanks,
Roland

  reply	other threads:[~2012-06-14 16:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14  0:09 Carlos O'Donell
2012-06-14  0:23 ` Roland McGrath
2012-06-14  6:54   ` Thomas Schwinge
2012-06-14 11:02   ` Joseph S. Myers
2012-06-14 16:47     ` Roland McGrath [this message]
2012-06-14 17:31       ` Mike Frysinger
2012-06-14  1:15 ` Mike Frysinger
2012-06-14  7:16   ` Andreas Jaeger
2012-06-14 14:31     ` Carlos O'Donell

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=20120614164730.CA15D2C0A4@topped-with-meat.com \
    --to=roland@hack.frob.com \
    --cc=carlos_odonell@mentor.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).