Commit message (Collapse) | Author | Age | ||
---|---|---|---|---|
... | ||||
* | | fsck: Now works in bare repositories. | 2011-10-29 | ||
| | | | | | | | | | | | | | | | | | | Checks location log information, and file contents. Does not check that numcopies is satisfied, as .gitattributes information about numcopies is not available in a bare repository. In practice, that should not be a problem, since fsck is also run in a checkout and will check numcopies there. | |||
| * | (no commit message) | 2011-10-29 | ||
| | | ||||
* | | refactor | 2011-10-29 | ||
|/ | ||||
* | getting tired of repeating myself | 2011-10-29 | ||
| | ||||
* | (no commit message) | 2011-10-29 | ||
| | ||||
* | responsen | 2011-10-29 | ||
| | ||||
* | Merge branch 'master' of ssh://git-annex.branchable.com | 2011-10-29 | ||
|\ | ||||
* | | add a tip | 2011-10-29 | ||
| | | ||||
* | | clean up check selection code | 2011-10-29 | ||
| | | | | | | | | | | | | | | | | | | This new approach allows filtering out checks from the default set that are not appropriate for a command, rather than having to list every check that is appropriate. It also reduces some boilerplate. Haskell does not define Eq for functions, so I had to go a long way around with each check having a unique id. Meh. | |||
| * | (no commit message) | 2011-10-29 | ||
| | | ||||
| * | Added a comment | 2011-10-29 | ||
|/ | ||||
* | responsen | 2011-10-29 | ||
| | ||||
* | (no commit message) | 2011-10-29 | ||
| | ||||
* | (no commit message) | 2011-10-29 | ||
| | ||||
* | close | 2011-10-29 | ||
| | ||||
* | sheesh. seriously? | 2011-10-29 | ||
| | ||||
* | Merge branch 'master' of ssh://git-annex.branchable.com | 2011-10-29 | ||
|\ | ||||
* | | pebak | 2011-10-29 | ||
| | | ||||
| * | (no commit message) | 2011-10-29 | ||
|/ | ||||
* | Added a comment | 2011-10-29 | ||
| | ||||
* | (no commit message) | 2011-10-29 | ||
| | ||||
* | responsen | 2011-10-29 | ||
| | ||||
* | (no commit message) | 2011-10-29 | ||
| | ||||
* | Added a comment | 2011-10-29 | ||
| | ||||
* | (no commit message) | 2011-10-29 | ||
| | ||||
* | Revert "as far as I know, --bwlimit does not accept unit, it always takes ↵ | 2011-10-28 | ||
| | | | | | | | | kilobytes" This reverts commit aeb4e285eb2b3b880ab6b91c5b1f7fa29d7182cb. bup's --bwlimit does take a unit, unlike rsync's. | |||
* | as far as I know, --bwlimit does not accept unit, it always takes kilobytes | 2011-10-29 | ||
| | ||||
* | status: Now always shows the current repository, even when it does not ↵ | 2011-10-28 | ||
| | | | | appear in uuid.log. | |||
* | drop --from is now supported to remove file content from a remote. | 2011-10-28 | ||
| | ||||
* | cleanup | 2011-10-27 | ||
| | ||||
* | document the little-known get --from | 2011-10-27 | ||
| | ||||
* | update | 2011-10-27 | ||
| | ||||
* | Fail if --from or --to is passed to commands that do not support them. | 2011-10-27 | ||
| | ||||
* | do commit location changes to remote in copy --to | 2011-10-27 | ||
| | | | | | test suite pointed out that if a file was copied from B to A, and then A cloned, the clone ought to immediatly know it can get the file from A. | |||
* | cleanup | 2011-10-27 | ||
| | ||||
* | refactored and generalized pre-command sanity checking | 2011-10-27 | ||
| | ||||
* | uninit: Add guard against being run with the git-annex branch checked out. | 2011-10-27 | ||
| | ||||
* | wording | 2011-10-27 | ||
| | ||||
* | reap in onLocal | 2011-10-27 | ||
| | | | | Each onLocal call involves a new Annex state, so needs to clean up after it. | |||
* | improve config reading when operating on remote on same host | 2011-10-27 | ||
| | | | | | | | | | Before the config was read each time onLocal was called, and entirely redundantly since it's read for same-host remotes on startup. Also a minor bug fix: When rsyncing to a same-host remote, use the rsync-options from the repository that the user ran git-annex in, not those of the receiving repository. | |||
* | Sped up some operations on remotes that are on the same host. | 2011-10-27 | ||
| | | | | | | | | | | | | | | 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. | |||
* | status too | 2011-10-27 | ||
| | ||||
* | avoid showing parens for empty descriptions | 2011-10-27 | ||
| | ||||
* | Added a comment | 2011-10-27 | ||
| | ||||
* | Added a comment | 2011-10-27 | ||
| | ||||
* | (no commit message) | 2011-10-27 | ||
| | ||||
* | (no commit message) | 2011-10-27 | ||
| | ||||
* | Added a comment | 2011-10-26 | ||
| | ||||
* | Added a comment | 2011-10-26 | ||
| | ||||
* | (no commit message) | 2011-10-26 | ||
| |