Start in a non-git directory takes about 400ms

[plafue]

When opening atom in a directory that is not a git repository, git-plus takes substantial time to activate. These are the samples taken when opening atom in an empty directory: 318ms, 388ms, 416ms, 405ms, 418ms, 566ms, 399ms, 395ms, 415ms, 400ms.

In comparison, opening atom with git-plus in a git repository takes always under 10ms.

I'm running atom 1.40.1 with git-plus 8.7.1 under Linux.

Steps to reproduce:

1. mkdir git-plus-empty-test && cd git-plus-empty-test
2. atom .
3. Open timecop

[akonwi]

Whoa, that's really weird. Yea that's consistent on my computer too.

I just profiled the actual execution of this package's activation, it only takes at most 4ms in any window, regardless of whether there are any folders/repositories even though timecop reports a much bigger number. I'll have to investigate more but I imagine it's some of the auxillary stuff atom does around the package activation that might be padding the numbers.

[plafue]

Thanks for looking into this!