From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 69756 invoked by alias); 29 Dec 2019 23:57:26 -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 69748 invoked by uid 89); 29 Dec 2019 23:57:26 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 spammy=wrap, H*i:sk:f237f0d, H*MI:sk:f237f0d, H*f:sk:f237f0d X-HELO: us-smtp-1.mimecast.com Received: from us-smtp-delivery-1.mimecast.com (HELO us-smtp-1.mimecast.com) (207.211.31.120) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 29 Dec 2019 23:57:25 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1577663843; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=i1FHRVnBxwRXGLtWyJWB93ZupfR4eOdJwjHQP88bpYE=; b=cu7BHSyAwIhDxK1AC2VtTf+A6PDg9BM9hvIIVHbIZtci5PhMd/Eag/LrXYus0VnlDA0U9U Gk5+iY5aaYwBKkiPmDsj9tDOXV/pUeD3FuLI5Lrw9jku82t0kiFOnVHN79Z7IobLC63gkW vlPZEJcpl3oMO533gqEERz09RgWcW+k= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-193-Ru7C2DBPMs6ybLUe-Ft_8Q-1; Sun, 29 Dec 2019 18:57:20 -0500 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id C4FDE800D41; Sun, 29 Dec 2019 23:57:18 +0000 (UTC) Received: from ovpn-112-19.phx2.redhat.com (ovpn-112-19.phx2.redhat.com [10.3.112.19]) by smtp.corp.redhat.com (Postfix) with ESMTP id 100E4107A44F; Sun, 29 Dec 2019 23:57:17 +0000 (UTC) Message-ID: Subject: Re: Proposal for the transition timetable for the move to GIT From: Jeff Law Reply-To: law@redhat.com To: Thomas Koenig , Segher Boessenkool , Julien '_FrnchFrgg_' RIVAUD Cc: gcc@gcc.gnu.org Date: Sun, 29 Dec 2019 23:57:00 -0000 In-Reply-To: References: <20191226183553.GK10088@tucnak> <20191228121921.GW4505@gate.crashing.org> <20191228202824.GZ4505@gate.crashing.org> <20191229104100.GA3191@gate.crashing.org> <98729b61-2322-4244-7bde-f29c7e654d59@free.fr> <20191229132649.GC3191@gate.crashing.org> User-Agent: Evolution 3.34.2 (3.34.2-1.fc31) MIME-Version: 1.0 X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2019-12/txt/msg00529.txt.bz2 On Sun, 2019-12-29 at 22:30 +0100, Thomas Koenig wrote: > Am 29.12.19 um 14:26 schrieb Segher Boessenkool: > > We cannot waste a year on a social experiment. We can slowly and carefully > > adopt new procedures, certainly. But anything drastic isn't advisable imo. > > > > Also, many GCC developers aren't familiar with Git at all. It takes time > > to learn it, and to learn new ways of working. Small steps are needed. > > Amen to that. > > My uses of git have can be counted in a single digit (in decimal). I am > just hoping you guys know what you are doing, and I am a bit > apprehensive about the change and my continued ability to contribute. > > Talk of a radical new development model does not raise my confidence. I was fairly anti GIT for a while, but there's simplistic workflows you can use which will be close enough to SVN that you're really just changing the commands you're using, not your entire workflow. You can add in "git specific" workflows later as you've become familiar with the basics. That's what I did, and boy once you wrap your head around git rebase for dealing with work in progress it's a game changer. jeff