author | Shawn O. Pearce <spearce@spearce.org> | |
Sun, 12 Nov 2006 22:58:08 +0000 (17:58 -0500) | ||
committer | Shawn O. Pearce <spearce@spearce.org> | |
Mon, 13 Nov 2006 05:10:38 +0000 (00:10 -0500) | ||
commit | 4658b56fce4e8b7c4489ae7b0fe9ecf1e236b70b | |
tree | da7164ffe0fc5fd8267b92d1542a3a1e54f48ce9 | tree | snapshot |
parent | ebf336b9422302ec89bce14b83017060d7ccd3e6 | commit | diff |
git-gui: Run the pre-commit hook in the background.
I started to notice on Windows that commits took a lot longer to get
going than on my Mac OS X system. The real reason is the repositories
that I'm testing with on Windows all enabled the standard pre-commit hook
while my test repository on Mac OS X doesn't have it executable (so its
not running). So the Windows repositories are spending this
lag time running that hook.
Now we run the pre-commit hook in the background, allowing the UI to
update and tell the user we are busy doing things.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
I started to notice on Windows that commits took a lot longer to get
going than on my Mac OS X system. The real reason is the repositories
that I'm testing with on Windows all enabled the standard pre-commit hook
while my test repository on Mac OS X doesn't have it executable (so its
not running). So the Windows repositories are spending this
lag time running that hook.
Now we run the pre-commit hook in the background, allowing the UI to
update and tell the user we are busy doing things.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
git-gui | diff | blob | history |