From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3417 invoked by alias); 21 May 2019 16:44:34 -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 3408 invoked by uid 89); 21 May 2019 16:44:33 -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,T_FILL_THIS_FORM_SHORT autolearn=ham version=3.3.1 spammy=HX-Languages-Length:986, history X-HELO: gate.crashing.org Received: from gate.crashing.org (HELO gate.crashing.org) (63.228.1.57) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 21 May 2019 16:44:32 +0000 Received: from gate.crashing.org (localhost.localdomain [127.0.0.1]) by gate.crashing.org (8.14.1/8.14.1) with ESMTP id x4LGiO1V005127; Tue, 21 May 2019 11:44:25 -0500 Received: (from segher@localhost) by gate.crashing.org (8.14.1/8.14.1/Submit) id x4LGiNpi005126; Tue, 21 May 2019 11:44:23 -0500 Date: Tue, 21 May 2019 16:44:00 -0000 From: Segher Boessenkool To: Joseph Myers Cc: Richard Sandiford , Maxim Kuvyrkov , Jeff Law , Richard Guenther , GCC Patches , Jason Merrill , Paolo Bonzini Subject: Re: [Contrib PATCH] Add scripts to convert GCC repo from SVN to Git Message-ID: <20190521164423.GH31586@gate.crashing.org> References: <26dcda27-15d5-2353-e1b8-2b90767671fe@redhat.com> <5E177D72-FE87-49FF-BAC7-0FB953CF9122@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-IsSubscribed: yes X-SW-Source: 2019-05/txt/msg01430.txt.bz2 Hi Joseph, On Mon, May 20, 2019 at 10:42:45PM +0000, Joseph Myers wrote: > (SVN will remain > readonly, just as the old CVS repository remains available readonly). > That the git-svn mirror is useful for many purposes for which people want > to use git also provides a clear argument against needing to do the final > conversion in a hurry; Right. But trying to correct the ancient history in the repo isn't useful *anyway*. One much bigger problem is that very often very unrelated things are committed at the same time, in big omnibus patches. Another much bigger problm is that when you are doing the kind of archeology where this matters, you need to have old the email archives anyway, which aren't available. > I think having author names and email addresses is a basic requirement of > any reasonable repository conversion Yes, and they should be the same as they were in the original repository. Segher