373cad993d
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. |
||
|---|---|---|
| .. | ||
| changelog | ||
| compat | ||
| control | ||
| copyright | ||
| doc-base | ||
| manpages | ||
| NEWS | ||
| rules | ||