From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29441 invoked by alias); 25 Dec 2019 14:16:41 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 29403 invoked by uid 89); 25 Dec 2019 14:16:34 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 spammy=genuinely X-HELO: digraph.polyomino.org.uk Received: from digraph.polyomino.org.uk (HELO digraph.polyomino.org.uk) (81.187.227.50) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 25 Dec 2019 14:16:33 +0000 Received: from jsm28 (helo=localhost) by digraph.polyomino.org.uk with local-esmtp (Exim 4.90_1) (envelope-from ) id 1ik7Sb-0004mo-AE; Wed, 25 Dec 2019 14:16:25 +0000 Date: Wed, 25 Dec 2019 14:16:00 -0000 From: Joseph Myers To: Segher Boessenkool cc: "Eric S. Raymond" , Alexandre Oliva , Jeff Law , Mark Wielaard , Maxim Kuvyrkov , "Richard Earnshaw (lists)" , gcc@gcc.gnu.org Subject: Re: Proposal for the transition timetable for the move to GIT In-Reply-To: <20191225122449.GL4505@gate.crashing.org> Message-ID: References: <20191216133632.GC3152@gate.crashing.org> <20191216135451.GA3142@thyrsus.com> <20191216140514.GD3152@gate.crashing.org> <20191216153649.GE3152@gate.crashing.org> <20191225120747.GA96669@thyrsus.com> <20191225122449.GL4505@gate.crashing.org> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-SW-Source: 2019-12/txt/msg00407.txt.bz2 On Wed, 25 Dec 2019, Segher Boessenkool wrote: > On Wed, Dec 25, 2019 at 07:07:47AM -0500, Eric S. Raymond wrote: > > For each of these exceptional commits a converter to Git has a choice > > of dropping the commit, turning it into some sort of annotated tag, or > > leaving it in place as a zero-op commit (anomalous but not forbidden > > in the git model). > > Or doing what everyone else does: put an empty .gitignore file in > otherwise empty directories. This is safe even if your conversion > creates such files from metadata (why on earth would you do that?!) An empty .gitignore is only needed in the case where the empty directory is genuinely needed. I'm pretty sure that none of those in GCC are needed, especially given that building in the source tree has been discouraged for a very long time so an empty directory shouldn't be present for use in the build; the most common reason (empirically) to have an empty directory in the source tree is that someone deleted the contents using git-svn to push the commit back to SVN (which thus only deleted the contents, and not the directory itself, in SVN). -- Joseph S. Myers jsm@polyomino.org.uk