From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <libc-alpha-return-90069-listarch-libc-alpha=sources.redhat.com@sourceware.org>
Received: (qmail 23872 invoked by alias); 6 Feb 2018 20:31:00 -0000
Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <libc-alpha.sourceware.org>
List-Subscribe: <mailto:libc-alpha-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/libc-alpha/>
List-Post: <mailto:libc-alpha@sourceware.org>
List-Help: <mailto:libc-alpha-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: libc-alpha-owner@sourceware.org
Received: (qmail 1119 invoked by uid 89); 6 Feb 2018 20:30:50 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.0 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE,SPF_HELO_FAIL,T_RP_MATCHES_RCVD autolearn=no version=3.3.2 spammy=Fwd
X-HELO: mx1.redhat.com
Subject: Re: Fwd: [PATCH v2 3/5] Don't install libio.h or _G_config.h.
To: Zack Weinberg <zackw@panix.com>, GNU C Library <libc-alpha@sourceware.org>
References: <cover.1517872307.git.zackw@panix.com>
 <cee6a6e4550535ac710797713d0ed5398beff6a4.1517872307.git.zackw@panix.com>
 <86ef9a83-8d98-be13-888f-281351945c27@linaro.org>
 <CAKCAbMiGUH5cBcZQjdf_uHTbqPyTJhBR-o8zo6u+hd_WCA_4VQ@mail.gmail.com>
 <CAKCAbMigr2f6HEJXTuDQseeCkFTzgd_as27Hj102e2AnB2kOfQ@mail.gmail.com>
From: Florian Weimer <fweimer@redhat.com>
Message-ID: <104b93df-d984-398d-8c65-79814d990a07@redhat.com>
Date: Tue, 06 Feb 2018 21:34:00 -0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <CAKCAbMigr2f6HEJXTuDQseeCkFTzgd_as27Hj102e2AnB2kOfQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2018-02/txt/msg00215.txt.bz2

On 02/06/2018 09:08 PM, Zack Weinberg wrote:
> These are good suggestions for further cleanups but I'm not going to
> fold them into this patchset.  I don't think there's any danger of
> them getting forgotten about; whoever next looks at libio(P).h is
> going to be looking for cleanups.

I completely agree with this approach.

Thanks,
Florian