Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | sync --content: Fix bug that caused transfers of files to be made to a git ↵ | 2016-06-02 | |
| | | | | | | | | | | | remote that does not have a UUID. This particularly impacted clones from gcrypt repositories. Added guard in Annex.Transfer to prevent this problem at a deeper level. I'm unhappy ith NoUUID, but having Maybe UUID instead wouldn't help either if nothing checked that there was a UUID. Since there legitimately need to be Remotes that do not have a UUID, I can't see a way to fix it at the type level, short making there be two separate types of Remotes. | ||
* | (no commit message) | 2016-05-28 | |
| | |||
* | (no commit message) | 2016-05-24 | |
| | |||
* | (no commit message) | 2016-05-24 | |
| | |||
* | (no commit message) | 2016-05-24 | |
| | |||
* | (no commit message) | 2016-05-24 | |