Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | scaled | 2011-03-04 | |
| | |||
* | headings | 2011-03-04 | |
| | |||
* | remove links llinked to above | 2011-03-04 | |
| | |||
* | format | 2011-03-04 | |
| | |||
* | format | 2011-03-04 | |
| | |||
* | format | 2011-03-04 | |
| | |||
* | format | 2011-03-04 | |
| | |||
* | format | 2011-03-04 | |
| | |||
* | format | 2011-03-04 | |
| | |||
* | format | 2011-03-04 | |
| | |||
* | update | 2011-03-04 | |
| | |||
* | prep for release | 2011-03-03 | |
| | |||
* | updates | 2011-03-03 | |
| | |||
* | Bugfix: When fsck detected and moved away corrupt file content, it did not ↵ | 2011-03-03 | |
| | | | | update the location log. | ||
* | remove debugging printf | 2011-03-03 | |
| | |||
* | support git funky remote syntaxes | 2011-03-03 | |
| | | | | | | * Look for dir.git directories the same as git does. * Support remote urls specified as relative paths. * Support non-ssh remote paths that contain tilde expansions. | ||
* | remove unused code | 2011-03-03 | |
| | |||
* | avoid failing if a local repo is not currently available | 2011-03-03 | |
| | | | | | | The added check if a repo is bare means its config needs to be read, but in this case it cannot be. That means that a repo currently not available is assumed to be non-bare. | ||
* | formatting | 2011-03-03 | |
| | |||
* | update | 2011-03-03 | |
| | |||
* | better quoting of description via show | 2011-03-03 | |
| | |||
* | add describe subcommand | 2011-03-03 | |
| | |||
* | document describe command | 2011-03-03 | |
| | |||
* | fix up commands that are trouble on bare repos | 2011-03-03 | |
| | | | | | Most will just abort. init does a basic init and gives a command to run elsewhere to finish it. | ||
* | prevent trust commands from trying to do things in a bare repo | 2011-03-03 | |
| | | | | | Since they need to stage changes, they would actually, if allowed to run, succeed, but wipe out existing trust.log content. | ||
* | updates for bare repo support | 2011-03-03 | |
| | |||
* | wow, non-local bare repos just worked | 2011-03-03 | |
| | |||
* | initial documantation/todo list for bare repositories | 2011-03-03 | |
| | |||
* | avoid logging to location log when in a bare repo | 2011-03-03 | |
| | | | | | | | | | | | | | | This assumes that changes to content in bare repos are made from some non-bare repo, and that the location log is updated on that side. That's true for move --from and move --to. It's *not* true for dropkey and setkey and recvkey. But those are plumbing level commands, so I guess it's ok to assume that someone running those in a bare repo knows what they're doing. And git-annex-shell is used to run those, and if the bare repo is non-local, it needs to be able to use them even though they cannot update the location log. So this seems unavoidable. | ||
* | remove redundant imports | 2011-03-03 | |
| | |||
* | some initial support for local bare repos | 2011-03-03 | |
| | | | | | | | | | | | This relies on git-annex's behavior of reading the config of local repos. That allows repoIsLocalBare to examine the git config for core.bare. Hopefully, gitAnnexLocation, gitAnnexDir, and gitAnnexObjectDir are only used on local repos. But, I have not audited fully, since they're probably not (see for example copyToRemote). And so, the functions fall back to their old non-bare-aware behavior for non-local repos. | ||
* | cannot be broken symlinks after all.. one other idea | 2011-03-03 | |
| | |||
* | amend | 2011-03-03 | |
| | |||
* | doesn't seem possible.. | 2011-03-03 | |
| | |||
* | (no commit message) | 2011-03-03 | |
| | |||
* | fsck: Check for and repair location log damage. | 2011-03-02 | |
| | |||
* | only enable SHA backends that configure finds support for | 2011-03-02 | |
| | |||
* | don't forget to rewrite tags | 2011-03-02 | |
| | |||
* | Found temporary solution | 2011-03-02 | |
| | |||
* | (no commit message) | 2011-03-02 | |
| | |||
* | Added a comment | 2011-03-02 | |
| | |||
* | link | 2011-03-01 | |
| | |||
* | format | 2011-03-01 | |
| | |||
* | add internals page | 2011-03-01 | |
| | |||
* | New backends: SHA512 SHA384 SHA256 SHA224 | 2011-03-01 | |
| | |||
* | generic SHA size support | 2011-03-01 | |
| | |||
* | bug | 2011-03-01 | |
| | |||
* | a slightly annoying thing | 2011-03-01 | |
| | |||
* | Added a comment | 2011-03-01 | |
| | |||
* | rename | 2011-02-28 | |
| |