From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Sven Axelsson Newsgroups: gmane.emacs.devel Subject: Re: Switching from old git tree Date: Fri, 14 Nov 2014 15:20:53 +0100 Message-ID: References: <87ioiiotwx.fsf@fencepost.gnu.org> <87egt5q46l.fsf@fencepost.gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: ger.gmane.org 1415974871 6759 80.91.229.3 (14 Nov 2014 14:21:11 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 14 Nov 2014 14:21:11 +0000 (UTC) Cc: emacs To: David Kastrup Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Nov 14 15:21:04 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1XpHkF-0004i1-Cu for ged-emacs-devel@m.gmane.org; Fri, 14 Nov 2014 15:21:03 +0100 Original-Received: from localhost ([::1]:36739 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XpHkE-0001Io-Rz for ged-emacs-devel@m.gmane.org; Fri, 14 Nov 2014 09:21:02 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39522) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XpHkB-0001IK-Aw for emacs-devel@gnu.org; Fri, 14 Nov 2014 09:21:00 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XpHkA-0000Va-BS for emacs-devel@gnu.org; Fri, 14 Nov 2014 09:20:59 -0500 Original-Received: from mail-vc0-x22f.google.com ([2607:f8b0:400c:c03::22f]:63760) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XpHk6-0000V2-FD; Fri, 14 Nov 2014 09:20:54 -0500 Original-Received: by mail-vc0-f175.google.com with SMTP id hy10so903630vcb.34 for ; Fri, 14 Nov 2014 06:20:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=hqn0aiSSy6e0b1xwCV7wTYpkEER83Q/onfTjqlXEngU=; b=yXFnlmldKAgMTIB3VgIw0M0Ae+bXMlRFarnl/jfo5S6aeXj9pSg/THqXHikqRqlD6T q628R+Zq/lTB/ejGucLgKXB8x+T4U2a1QE+mj7SCD13KTR9QZtvi5QeuhUgyBiuogQ+V 3TxsHr8tfuSJDF0hJDzrGt7IT0sQ+4SoubncN8gOC0uHEBNxURygZJVhYRzImn29xi3B aBRLVraDQht4Qm9PbZ4r3XUPKLmpJG4y4wVwsvCoACg8MP/yjiRiaCEY1ElLLmSQOPaD T3fNhF8r5FNxsA2+ykXYvyWnQDXe0wiDSyUUUOr3xHt3M8+XG2Rq9JkKFZnwCbEgUlBd 8D+g== X-Received: by 10.52.187.67 with SMTP id fq3mr5902664vdc.22.1415974853985; Fri, 14 Nov 2014 06:20:53 -0800 (PST) Original-Received: by 10.31.153.4 with HTTP; Fri, 14 Nov 2014 06:20:53 -0800 (PST) In-Reply-To: <87egt5q46l.fsf@fencepost.gnu.org> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:400c:c03::22f X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:177083 Archived-At: On 14 November 2014 14:53, David Kastrup wrote: > Sven Axelsson writes: >> I suppose you could add your old repo as a local remote to the new one, and >> cherry-pick your commits, i.e.: >> >> git remote add old /local/path/to/old >> # Fetch the data to your new repo >> git fetch old >> # Find the commits to pick somehow >> git log old/master >> # Copy to new repo >> git cherry-pick > > Well, I was trying to avoid the "double your repository size or no money > back" effect. While the file and tree blobs in two differently > converted Emacs repositories are presumably pretty much the same, the > entire commit history is disjoint. Once it takes root in your > repository, it will take a long long time before it gets washed out > again _after_ removing all branches/references to it. Going through > patches minimizes the data the new repository gets to see from the old > one. Sure, but does the repo size really matter? We are not talking about data that is transmitted upstream. Also, isn't it sufficient to do git remote rm old git gc to clean out the repo? I haven't looked into it so I'm curious. -- Sven Axelsson ++++++++++[>++++++++++>+++++++++++>++++++++++>++++++ >++++<<<<<-]>++++.+.++++.>+++++.>+.<<-.>>+.>++++.<<. +++.>-.<<++.>>----.<++.>>>++++++.<<<<.>>++++.<----.