Sped up some operations on remotes that are on the same host.

Specifically, disabled trying to update the git-annex branch on the remote,
since that data is never used by operations that act on such remotes.

Also, when copying content to such a remote, skip committing the presence
information changes to its git-annex branch. Leaving it in the journal there
is ok: Any command run on the remote that needs the info will flush the
journal.

This may partially solve this bug:
http://git-annex.branchable.com/bugs/fails_to_handle_lot_of_files/
Although I still see unreaped git processes piling up when doing a copy --to.
This commit is contained in:
Joey Hess 2011-10-27 14:04:18 -04:00
parent 2eefc58070
commit 373cad993d
3 changed files with 25 additions and 9 deletions

6
debian/changelog vendored
View file

@ -1,3 +1,9 @@
git-annex (3.20111026) UNRELEASED; urgency=low
* Sped up some operations on remotes that are on the same host.
-- Joey Hess <joeyh@debian.org> Thu, 27 Oct 2011 13:58:53 -0400
git-annex (3.20111025) unstable; urgency=low
* A remote can have a annexUrl configured, that is used by git-annex