From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 108662 invoked by alias); 13 Sep 2019 07:20:23 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 108650 invoked by uid 89); 13 Sep 2019 07:20:23 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS,T_FILL_THIS_FORM_SHORT autolearn=ham version=3.3.1 spammy=mails, H*r:192.168.43, gcc-cvs, gcccvs X-HELO: mail-lj1-f194.google.com Received: from mail-lj1-f194.google.com (HELO mail-lj1-f194.google.com) (209.85.208.194) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 13 Sep 2019 07:20:19 +0000 Received: by mail-lj1-f194.google.com with SMTP id d5so26068494lja.10 for ; Fri, 13 Sep 2019 00:20:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=/ZZvgWUYa/HSwkf8fjriIKDpkEpmNxupsS1inV/nJFI=; b=V2o0Uk9EzpjpC9+vtEfwovkzPSWWoCsmUA/U/ZmVyNDTB9F7Pid30bMXB+Gkf3Ej+A 1ZhzJOnNncVqjFdMmavMj78uNorqvlRUhxjFFxG6atD0JHW0icXffW++ORSrDc+sQlp+ xgTiU8LNKLwG1BDdlnlqD+qUvuAwo9ZwSozS4GTqaz4mf2C0WFCxzCBjfQByI7NkBN3v kAczTLR/kGQ6S+6AlRSPtG8wAW5/rIMikNDlb4pTczLdiZDmA8SeoCZJ9NHg3PQuXJs2 Fos1L56zIJFupFG1PQ9It50+3Zx9S1H/4gy7UM7HcSzPeWlRatEh085j2+CGfNIXB8nE tiww== Return-Path: Received: from [192.168.43.225] ([31.173.85.78]) by smtp.gmail.com with ESMTPSA id d12sm6757083lfn.93.2019.09.13.00.20.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 13 Sep 2019 00:20:15 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: [Contrib PATCH] Add scripts to convert GCC repo from SVN to Git From: Maxim Kuvyrkov In-Reply-To: Date: Fri, 13 Sep 2019 07:20:00 -0000 Cc: GCC Patches , Jason Merrill , Paolo Bonzini , Richard Guenther , =?utf-8?Q?Martin_Li=C5=A1ka?= Content-Transfer-Encoding: quoted-printable Message-Id: References: <8C62F814-2F57-4D1A-B66F-5C5ACFF37D6C@linaro.org> <4E46E435-F95C-46AD-87F0-8220D2BF4CD4@linaro.org> <7FA7C370-04F5-448E-95D2-426607B99CF4@linaro.org> <846D2EF4-879F-4518-ABA5-7DD74E6B4F18@linaro.org> <7835E1FD-DE75-4F0E-81E5-1B23CFBDD884@linaro.org> <7A734FBC-74CF-43AC-AADA-29809F2CD3AC@linaro.org> To: "Joseph S. Myers" X-SW-Source: 2019-09/txt/msg00871.txt.bz2 > On Aug 24, 2019, at 12:30 AM, Joseph Myers wrot= e: >=20 > On Fri, 23 Aug 2019, Maxim Kuvyrkov wrote: >=20 >> I propose that we switch to gcc-pretty.git repository, because it has=20 >> accurate Committer and Author fields. Developer names and email=20 >> addresses are extracted from source history, and accurately track people= =20 >> changing companies, email addresses, and names. IMO, it is more=20 >> important for people to get credit for open-source contributions on=20 >> github, ohloh, etc., than the inconvenience of rebasing local git=20 >> branches. It's also an important marketing tool for open-source=20 >> companies to show stats of their corporate email addresses appearing in= =20 >> git commit logs. >=20 > I concur that accurately crediting contributors is important and means we= =20 > should not start from the existing mirror (though we should keep its=20 > branches available, so references to them and to their commit hashes=20 > continue to work - either keeping the existing repository available under= =20 > a different name, or renaming the branches to put them in the new=20 > repository - which should not enlarge the repository much because blob an= d=20 > tree objects will generally be shared between the two versions of the=20 > history). >=20 > I note that the Go conversion of reposurgeon is now just five test=20 > failures away from passing the whole reposurgeon testsuite (at which poin= t=20 > it should be ready for an attempt on the GCC conversion). Given the good= =20 > progress being made there at present, I thus suggest we plan to compare=20 > this conversion with one from reposurgeon (paying special attention to th= e=20 > messiest parts of the repository, such as artifacts from cvs2svn=20 > attempting to locate branchpoints), unless those last five goreposurgeon= =20 > test failures prove unexpectedly time-consuming to get resolved. Could you upload GCC repo converted with reposurgeon somewhere public? And= also list expected artifacts in its current version? >From my side, the machine on which the conversion ran ran out of disk spac= e about 3 weeks ago. I'll clean it up and restart the conversion updates. I'll also improve author entries a bit, so gcc-pretty.git's history will ch= ange ever so slightly. >=20 > There are of course plenty of things to do relating to a git conversion=20 > that do not depend on the particular choice of a converted repository -=20 > such as writing git hooks and git versions of the maintainer-scripts=20 > scripts that currently work with SVN, or working out a specific choice of= =20 > how to arrange annotated tags to allow "git describe" to give the sort of= =20 > monotonic version number some contributors want. >=20 > A reasonable starting point for hooks would be that they closely=20 > approximate what the current SVN hooks do for commit mails to gcc-cvs and= =20 > for Bugzilla updates, as what the current hooks do is clearly OK at=20 > present and we shouldn't need to entangle substantive changes to what the= =20 > hooks do with the actual conversion to git; we can always discuss changes= =20 > later. Would the community please assign a volunteer for this at Cauldron? :-P Thank you, -- Maxim Kuvyrkov www.linaro.org