From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <libc-alpha-return-59206-listarch-libc-alpha=sources.redhat.com@sourceware.org>
Received: (qmail 67495 invoked by alias); 22 May 2015 22:10:17 -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 67396 invoked by uid 89); 22 May 2015 22:10:15 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=0.3 required=5.0 tests=AWL,BAYES_20,KAM_LAZY_DOMAIN_SECURITY,LIKELY_SPAM_SUBJECT autolearn=no version=3.3.2
X-HELO: topped-with-meat.com
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Roland McGrath <roland@hack.frob.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: libc-alpha@sourceware.org
Subject: Re: [PROPOSED PATCH] Convert source files to UTF-8
In-Reply-To: Paul Eggert's message of  Friday, 22 May 2015 14:51:39 -0700 <555FA4EB.1010401@cs.ucla.edu>
References: <555FA4EB.1010401@cs.ucla.edu>
Message-Id: <20150522221011.DF1F42C3ABD@topped-with-meat.com>
Date: Sun, 24 May 2015 02:23:00 -0000
X-CMAE-Score: 0
X-CMAE-Analysis: v=2.1 cv=SvUDtp+0 c=1 sm=1 tr=0
		a=WkljmVdYkabdwxfqvArNOQ==:117 a=14OXPxybAAAA:8 a=kj9zAlcOel0A:10
		a=hOe2yjtxAAAA:8 a=HzafoORq0eH7hEEVnHwA:9 a=CjuIK1q_8ugA:10
X-SW-Source: 2015-05/txt/msg00562.txt.bz2

Converting old ChangeLog files (or any other files not involved in the
build or install) is an "obvious enough".  Just do that on its own and
commit it.

Then for further changes you can follow our protocol, which requires
including the ChangeLog entries in the message outside any patch or
attachment.  That makes it reasonable to have a review thread at all
for a patch that has to be in an encoded attachment.

What I'd recommend for the first set of changes is replacing non-ASCII
literal bytes in strings with C escapes, and any conversions in comments
or string literals in any file.  That's a change for which you can report
that you've verified the build products are completely unchanged before
and after the change.  Then it needs barely any review, and can go in
very quickly.

Attack the other changes after those are in.


Thanks,
Roland