Git Manager 1.2.3

This release makes Git Manager faster and lighter on large repositories: long histories, searches with many results and thousands of changed files.

Improvements

Faster history on big repositories: Git Manager now creates Git's commit-graph file in the background for repositories that don't have one, and keeps it up to date after fetch and pull. On a repository with 100,000 commits, each page of history loads about 3–4 times faster.
Searches stay light: message and author searches now show their results as a single column instead of a graph. A search with many results could previously draw a graph thousands of pixels wide, and memory use rose by several hundred megabytes.
Thousands of changed files: the Changes list and the commit inspector's file list draw only the rows on screen. With 7,500 changed files, typing a commit message, moving with the arrow keys and Select all now respond instantly, and memory use stays about the same as with a few files.
Less work in the background:
- Refreshes that find nothing new no longer redraw the window.
- Staging and discarding no longer reload the history.
- While the window is minimized or hidden, file changes are noted and caught up in one refresh when it comes back.
- Each refresh starts fewer Git processes.
- Repositories with more than 5,000 new files no longer run git status twice on every refresh.

Switching to Changes right after Git Manager starts could leave a commit's diff from History on screen, and choosing a file didn't replace it. The working copy now stays selected.