From: Joseph Myers <joseph@codesourcery.com>
To: "Maciej W. Rozycki" <macro@mips.com>
Cc: Stefan Liebler <stli@linux.vnet.ibm.com>, <libc-alpha@sourceware.org>
Subject: Re: [PATCH] nisplus: Correct pwent parsing issue and resulting compilation error
Date: Mon, 18 Jun 2018 15:49:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1806181549080.23315@digraph.polyomino.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.00.1806181635290.20622@tp.orcam.me.uk>
On Mon, 18 Jun 2018, Maciej W. Rozycki wrote:
> > as I said in <https://sourceware.org/ml/libc-alpha/2018-03/msg00532.html>
> > it would be a very good idea to add a --enable-obsolete-rpc
> > --enable-obsolete-nsl configuration to build-many-glibcs.py so issues
> > building such a configuration with new GCC get detected and fixed quicker.
>
> Hmm, but why it's been 2+ months and such an obvious fix hasn't been
> reviewed yet? Insufficient pinging?
Only pinged once as far as I can see. Quite likely most developers aren't
using those configure options and so aren't affected by the issue.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2018-06-18 15:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 15:10 Maciej W. Rozycki
2018-06-18 15:25 ` Joseph Myers
2018-06-18 15:45 ` Maciej W. Rozycki
2018-06-18 15:49 ` Joseph Myers [this message]
2018-06-18 15:41 ` Andreas Schwab
2018-06-18 16:13 ` [PATCH v2] nisplus: Correct pwent parsing issue and resulting compilation error [BZ #23266] Maciej W. Rozycki
2018-06-18 19:44 ` DJ Delorie
2018-06-18 20:11 ` Maciej W. Rozycki
2018-06-18 20:40 ` DJ Delorie
2018-06-25 19:17 ` [PING][PATCH " Maciej W. Rozycki
2018-06-26 1:32 ` DJ Delorie
2018-06-27 20:14 ` [committed v3] nisplus: Correct pwent parsing issue and resulting build " Maciej W. Rozycki
2018-06-27 21:03 ` Joseph Myers
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=alpine.DEB.2.20.1806181549080.23315@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=macro@mips.com \
--cc=stli@linux.vnet.ibm.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).