diff options
| author |  Joey Hess <joey@kitenet.net> | 2013-12-16 15:43:28 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2013-12-16 16:16:19 -0400 |
| commit | 216bb57e1060dbf82c3c1ead19a7264b048372cf (patch) | |
| tree | b47f0e119da4a69ba058889603a8d411d31cf5f7 /debian | |
| parent | 2d80dac99cb3af02d013507f04a5a24d5be2e7ef (diff) | |
assistant: Always batch changes found in startup scan.
Batch detection is heuristic, so can sometimes fail. I observed one such
failure while starting up in a repository with 87000 files. After the first
several batches of ~5000 files, it fell out of batch mode, and never
re-entered it, and so made many more commits of a few files at a time
than necessary.
So, let's always use batch mode when in the startup scan. This avoids the
heuristic there, at least.
There is clearly also room to improve the heuristic. Possibly 10 files is
too high a bar to be found during a commit, on a system that can commit
quickly.
Diffstat (limited to 'debian')
| -rw-r--r-- | debian/changelog | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/debian/changelog b/debian/changelog index 8b8968c4d..628307671 100644 --- a/debian/changelog +++ b/debian/changelog @@ -10,6 +10,7 @@ git-annex (5.20131214) UNRELEASED; urgency=low * Include man pages in Linux and OSX standalone builds. * Linux standalone build now includes its own glibc and forces the linker to use it, to remove dependence on the host glibc. + * assistant: Always batch changes found in startup scan. -- Joey Hess <joeyh@debian.org> Sun, 15 Dec 2013 13:32:49 -0400 |