Re: suboptimal behavior of fast-import in some cases with from

On Mon, Jul 06, 2015 at 03:54:35PM -0700, Junio C Hamano wrote: Mike Hommey m...@glandium.org writes: One of the first things parse_from does is unconditionally throw away the tree for the given branch, and then the from tree is loaded. So when the from commit is the current head of the

Re: suboptimal behavior of fast-import in some cases with from

On Thu, Jul 09, 2015 at 02:03:15PM +0900, Mike Hommey wrote: On Mon, Jul 06, 2015 at 03:54:35PM -0700, Junio C Hamano wrote: Mike Hommey m...@glandium.org writes: One of the first things parse_from does is unconditionally throw away the tree for the given branch, and then the from tree

Re: suboptimal behavior of fast-import in some cases with from

Mike Hommey m...@glandium.org writes: One of the first things parse_from does is unconditionally throw away the tree for the given branch, and then the from tree is loaded. So when the from commit is the current head of the branch, that make fast-import do more work than necessary. If it is

suboptimal behavior of fast-import in some cases with from

Hi, I did something stupid with a script using fast-import, and that made the whole process ~20% slower on Linux and 400~500% slower on Mac. The reason this happened is that the script was essentially adding a from to every commit command, even when the from commit is the current head of the