Don't always use git-merge-recursive because of speed
commitf3b4fbfff9f3042a406f25b8201582c3351cd1ca
authorCatalin Marinas <catalin.marinas@gmail.com>
Fri, 8 Dec 2006 22:31:52 +0000 (8 22:31 +0000)
committerCatalin Marinas <catalin.marinas@gmail.com>
Fri, 8 Dec 2006 22:31:52 +0000 (8 22:31 +0000)
tree215682206b53aa5b882c1279687d4d8d5a1be886
parent06848faba60e1c4e637b15b608e5bd94989c4196
Don't always use git-merge-recursive because of speed

There are situations like picking patches, folding a patch onto a base
or synchronising patches where the distance between base and heads is
in general small. In this case, git-read-tree --aggressive is much
faster. We currently use the recursive merge when picking or pushing a
patch (the base change might involve some renames).

Signed-off-by: Catalin Marinas <catalin.marinas@gmail.com>
stgit/commands/pick.py
stgit/git.py
stgit/stack.py