Re: Switching from old git tree

[Sven Axelsson]

On 14 November 2014 14:53, David Kastrup <address@hidden> wrote:
> Sven Axelsson <address@hidden> 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 <sha-of-commit>
>
> 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
++++++++++[>++++++++++>+++++++++++>++++++++++>++++++
>++++<<<<<-]>++++.+.++++.>+++++.>+.<<-.>>+.>++++.<<.
+++.>-.<<++.>>----.<++.>>>++++++.<<<<.>>++++.<----.