Re: [PATCH] contrib/subtree: Split history with empty trees correctly

2016-02-02 Thread David A. Greene
Marcus Brinkmann writes: >> Are you still able to do a re-roll on this? > > I have to admit that my interest has declined steeply since > discovering that subtree-split and filter-branch --subtree-filter give > different results from "git svn" on the subdirectory. The reason is > that git-svn in

Re: [PATCH] contrib/subtree: Split history with empty trees correctly

2016-01-27 Thread Marcus Brinkmann
On 01/28/2016 03:56 AM, David A. Greene wrote: Marcus Brinkmann writes: With my patch, "git subtree split -P" produces the same result (for my data set) as "git filter-branch --subdirectory-filter", which is much faster, because it selects the revisions to rewrite before rewriting. As I am not

Re: [PATCH] contrib/subtree: Split history with empty trees correctly

2016-01-27 Thread David A. Greene
Marcus Brinkmann writes: > With my patch, "git subtree split -P" produces the same result (for my > data set) as "git filter-branch --subdirectory-filter", which is much > faster, because it selects the revisions to rewrite before rewriting. > As I am not using any of the advanced features of "gi

Re: [PATCH] contrib/subtree: Split history with empty trees correctly

2016-01-27 Thread David A. Greene
[ Sorry it took a few days to reply. I am absolutely slammed at work and will be for the next few weeks at least. The good news is that it's resulting in some nice work on git-subtree! :) ] Marcus Brinkmann writes: > On 01/20/2016 05:05 AM, David A. Greene wrote: >> Marcus Brinkmann writ

Re: [PATCH] contrib/subtree: Split history with empty trees correctly

2016-01-24 Thread Marcus Brinkmann
With my patch, "git subtree split -P" produces the same result (for my data set) as "git filter-branch --subdirectory-filter", which is much faster, because it selects the revisions to rewrite before rewriting. As I am not using any of the advanced features of "git subtree", I will just use "git fi