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.
This commit is contained in:
parent
19d5a5657e
commit
58c7b0a56d
3 changed files with 12 additions and 4 deletions
1
debian/changelog
vendored
1
debian/changelog
vendored
|
@ -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
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue