From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8480 invoked by alias); 17 Jul 2015 04:26:47 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 8410 invoked by uid 89); 17 Jul 2015 04:26:46 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-Spam-User: qpsmtpd, 2 recipients X-HELO: mail-wi0-f182.google.com Received: from mail-wi0-f182.google.com (HELO mail-wi0-f182.google.com) (209.85.212.182) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Fri, 17 Jul 2015 04:26:44 +0000 Received: by wibud3 with SMTP id ud3so30021457wib.1; Thu, 16 Jul 2015 21:26:41 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.194.91.232 with SMTP id ch8mr23961164wjb.19.1437107201352; Thu, 16 Jul 2015 21:26:41 -0700 (PDT) Received: by 10.28.50.129 with HTTP; Thu, 16 Jul 2015 21:26:41 -0700 (PDT) In-Reply-To: References: Date: Fri, 17 Jul 2015 04:26:00 -0000 Message-ID: Subject: Re: [PATCH] [4/14] Completes renaming of configure.in files to .ac From: Michael Darling To: "H.J. Lu" Cc: Binutils , GDB , GCC Patches Content-Type: text/plain; charset=UTF-8 X-SW-Source: 2015-07/txt/msg00502.txt.bz2 > Since all configure files are generated from them, this patch must be > checked in first. > But some of them are imported and some imported packages still use configure.in, > not configure.ac. > > What is the real value of changing "configure.in" in comments/messages to > "configure.ac" when both are used in packages? Before binutils commit 35eafcc7 a year ago, I'm pretty sure everything in binutils-gdb used the .in extension. And, around that time, I'm pretty sure everything in gcc also used the .in extension. Binutils-gdb partially moved over to the .ac extension, and gcc completely moved over to the .ac extension. This left a lot of references pointing to the wrong extension. Allowing both extensions, even if made to work now, will break again someday. I think having comments, messages, and documentation point semi-randomly to one or the other is inviting future confusion. I think the only way to permanently fix this is to complete the (almost complete) transition to the .ac extension. I would have probably personally left everything as a .in extension, since for now there's no real difference, but I think the transition should either be complete or not there at all. Since the conversion already started, I think all references anywhere to the .in extension should be updated. (Unless in a historical context like a ChangeLog.) Which imported packages use configure.in? I'm happy to submit patches for those, too.