| commit | 5a2018e13924063bde19b2e61b17cd7ed363b786 | |
| author | Shawn O. Pearce <spearce@spearce.org> | |
| Sat, 26 Apr 2008 00:28:26 +0000 (25 20:28 -0400) | ||
| committer | Shawn O. Pearce <spearce@spearce.org> | |
| Sun, 11 May 2008 05:16:29 +0000 (11 01:16 -0400) | ||
| tree | 7847342975aae605e4809cdcda5713fa96aaa62c | treesnapshot (tar.gz zip) |
| parent | b5ca2861157561e5bf94d6400f44e3ffba75880f | commitdiff |
Report progress on console if operation takes more than 500 ms
Rather than starting our timer on each task, we start the timer for
the overall operation, and instead of using a timeout of 1000 ms for
the first output we use 500 ms. In many cases jgit is fast enough
that we almost never see any sort of progress from it, even though
the same operation in C Git shows progress. Our timer was just a
tad too long and can leave the user wondering what we are doing.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Rather than starting our timer on each task, we start the timer for
the overall operation, and instead of using a timeout of 1000 ms for
the first output we use 500 ms. In many cases jgit is fast enough
that we almost never see any sort of progress from it, even though
the same operation in C Git shows progress. Our timer was just a
tad too long and can leave the user wondering what we are doing.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
| org.spearce.jgit/src/org/spearce/jgit/lib/TextProgressMonitor.java | diffblobblamehistory |