From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8248 invoked by alias); 13 Jan 2020 18:12:18 -0000 Mailing-List: contact libstdc++-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libstdc++-owner@gcc.gnu.org Received: (qmail 8232 invoked by uid 89); 13 Jan 2020 18:12:18 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.5 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.1 spammy=modern, gitlab, GitLab, *will* X-HELO: snark.thyrsus.com Received: from thyrsus.com (HELO snark.thyrsus.com) (71.162.243.5) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 13 Jan 2020 18:12:17 +0000 Received: by snark.thyrsus.com (Postfix, from userid 1000) id 862004704D82; Mon, 13 Jan 2020 13:12:15 -0500 (EST) Date: Mon, 13 Jan 2020 21:41:00 -0000 From: "Eric S. Raymond" To: Jonathan Wakely Cc: Joseph Myers , Sandra Loosemore , gcc-patches@gcc.gnu.org, libstdc++ Subject: Re: [PATCH] Clean up references to Subversion in documentation sources. Message-ID: <20200113181215.GA126826@thyrsus.com> Reply-To: esr@thyrsus.com References: <20200113140202.GA63759@thyrsus.com> <3f91720b-c6b3-533f-de39-26f200f5cc34@codesourcery.com> <20200113172455.GA88155@thyrsus.com> <20200113173523.GD60955@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200113173523.GD60955@redhat.com> User-Agent: Mutt/1.10.1 (2018-07-13) X-SW-Source: 2020-01/txt/msg00081.txt.bz2 Jonathan Wakely : > Email the patches to gcc-patches@gcc.gnu.org, that's how things get > merged. > > We're not looking to change any workflows now. Roger that. Once the dust from the conversion has settled, though, there is a related issue I intend to bring up on the main list. You've only collected about 60% of the potential benefits from git by adopting git itself. The other 40% would come from moving to to one of the modern git-centric forges like GitHub or GitLab. I'm as old-school as any of you guys, so take me seriously when I say these are not popular for merely faddish reasns. The integration of repository management, issue tracking, and continuous integration they offer really does offer a major step up in productivity and auditability. I *will* be nudging the GCC project community to think about this. -- Eric S. Raymond