From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6630 invoked by alias); 26 Dec 2019 19:16:11 -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 6618 invoked by uid 89); 26 Dec 2019 19:16:11 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.3 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.1 spammy=cutting, UD:catb.org, UD:www.catb.org, www.catb.org 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; Thu, 26 Dec 2019 19:16:09 +0000 Received: by snark.thyrsus.com (Postfix, from userid 1000) id F055B4704C33; Thu, 26 Dec 2019 14:16:07 -0500 (EST) Date: Thu, 26 Dec 2019 19:16:00 -0000 From: "Eric S. Raymond" To: Alexandre Oliva Cc: Jeff Law , Segher Boessenkool , Joseph Myers , Mark Wielaard , Maxim Kuvyrkov , "Richard Earnshaw (lists)" , gcc@gcc.gnu.org Subject: Re: Proposal for the transition timetable for the move to GIT Message-ID: <20191226191607.GA8608@thyrsus.com> Reply-To: esr@thyrsus.com References: <20191216133632.GC3152@gate.crashing.org> <20191216135451.GA3142@thyrsus.com> <20191216140514.GD3152@gate.crashing.org> <20191216153649.GE3152@gate.crashing.org> <20191225120747.GA96669@thyrsus.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-IsSubscribed: yes X-SW-Source: 2019-12/txt/msg00426.txt.bz2 Alexandre Oliva : > On Dec 25, 2019, "Eric S. Raymond" wrote: > > > Reposurgeon has a reparent command. If you have determined that a > > branch is detached or has an incorrect attachment point, patching the > > metadata of the root node to fix that is very easy. > > Thanks, I see how that can enable a missed branch to be converted and > added incrementally to a converted repo even after it went live, at > least as long as there aren't subsequent merges from a converted branch > to the missed one. I don't quite see how this helps if there are, > though. There's also a command for cutting parent links, ifvthat helps. > Could make it a requirement that at least the commits associated with > head branches and published tags compare equal in both conversions, or > that differences are known, understood and accepted, before we switch > over to either one? Going over all corresponding commits might be too > much, but at least a representative random sample would be desirable to > check IMHO. repotool compare does that, and there's a production in the conversion makefile that applies it. As Joseph says in anotyer reply, he's already doing a lot of the verifications you are suggesting. -- Eric S. Raymond