Doesn't deal well with large repos or lots of changes, even with `-e`

I suspect my speed issues with git-explode ( https://github.com/aspiers/git-explode/issues/6 ) come from git-deps. See that issue for stats on the size of the project. I can also provide things like commit depth on some of the files in question. I don't know if `git-explode` provides the `HEAD` argument to `git-deps -e`, but even when looking at the code with `git-deps -e main ...` it takes a VERY long time to run and seems to analyze a ton of hunks that are far beyond the `-e` commit.

Start with the linked git-explode issue for repository-size and timing statistics, then reproduce `git-deps -e main ...` on the affected repository. Trace which hunks are analyzed beyond the `-e` commit; done means the command avoids that unnecessary work and completes substantially faster.

Written by the indexing model from the issue text.