From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 117409 invoked by alias); 21 Sep 2017 17:17:25 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 117352 invoked by uid 89); 21 Sep 2017 17:17:23 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS,URIBL_RED autolearn=ham version=3.3.2 spammy=extras, telling X-Spam-User: qpsmtpd, 2 recipients X-HELO: relay1.mentorg.com Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 21 Sep 2017 17:17:20 +0000 Received: from nat-ies.mentorg.com ([192.94.31.2] helo=svr-ies-mbx-01.mgc.mentorg.com) by relay1.mentorg.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-SHA384:256) id 1dv56B-0000gK-0G from joseph_myers@mentor.com ; Thu, 21 Sep 2017 10:17:15 -0700 Received: from digraph.polyomino.org.uk (137.202.0.87) by svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Thu, 21 Sep 2017 18:17:11 +0100 Received: from jsm28 (helo=localhost) by digraph.polyomino.org.uk with local-esmtp (Exim 4.86_2) (envelope-from ) id 1dv563-0002MG-BK; Thu, 21 Sep 2017 17:17:07 +0000 Date: Thu, 21 Sep 2017 17:17:00 -0000 From: Joseph Myers To: Matt Rice CC: Fiodar Stryzhniou , Andreas Schwab , Petr Ovtchenkov , Binutils , Joel Brobecker , Matthias Klose , GDB Subject: Re: meaning of "Automatic date update in version.in" commits In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-ClientProxiedBy: svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) To svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) X-SW-Source: 2017-09/txt/msg00089.txt.bz2 On Thu, 21 Sep 2017, Matt Rice wrote: > option A. seems to be using git smudge/filter to on checkout populate > the version.in using a smudge rule, and then filtering it out using a > filter, > acting much like the RCS keywords... > pros: no extra commit stuff at all > cons: requires setting up git config stuff in the repository for > executing the smudge/filter rules on checkout > this should likely be checked by the configure process e.g. > configure should produce an error telling the user to enable the > smudge/filter rules > when the version is $Date$ rather an actual date... I don't think there should be anything that requires people to check out in a special way, or to configure their checkouts specially, rather than just using "git clone" and a subsequent build. Generic tools such as build bots may have generic knowledge of how to check out and update git checkouts; they should not need binutils-specific extras to that knowledge. -- Joseph S. Myers joseph@codesourcery.com