From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Carlos O'Donell <carlos@redhat.com>
Cc: GNU C Library <libc-alpha@sourceware.org>,
"libc-ports@sourceware.org" <libc-ports@sourceware.org>
Subject: Re: The hppa port is now moved out of ports.
Date: Tue, 29 Apr 2014 21:46:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1404292145160.14769@digraph.polyomino.org.uk> (raw)
In-Reply-To: <536019AC.1000602@redhat.com>
On Tue, 29 Apr 2014, Carlos O'Donell wrote:
> * Use libc-ports to highlight cross-port issues so maintainers
> need not pay close attention to libc-alpha.
I thought the conclusion was not to do that (that I was the only person
suggesting repurposing libc-ports like that), but developers not updating
all ports have the responsibility to draw attention to that fact and
update <https://sourceware.org/glibc/wiki/PortStatus> when checking in the
patch that only updates some ports.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2014-04-29 21:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 8:20 Carlos O'Donell
2014-04-29 15:21 ` Joseph S. Myers
2014-04-29 21:29 ` Carlos O'Donell
2014-04-29 21:46 ` Joseph S. Myers [this message]
2014-04-29 21:58 ` Carlos O'Donell
2014-04-29 22:07 ` Joseph S. Myers
2014-04-29 22:35 ` Carlos O'Donell
2014-04-30 17:44 ` Roland McGrath
2014-04-30 17:46 ` 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=Pine.LNX.4.64.1404292145160.14769@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=carlos@redhat.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).