Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | Merge branch 'master' of ssh://git-annex.branchable.com | 2015-08-11 | |
|\ | |||
* | | devblog | 2015-08-11 | |
| | | |||
* | | comment | 2015-08-11 | |
| | | |||
* | | clarify | 2015-08-11 | |
| | | |||
* | | avoid nul-truncation | 2015-08-11 | |
| | | | | | | | | | | | | | | This might be a little slower, but it's safer, in the event that a union-merged file contains a NUL. AFAIK, no files in the git-annex branch do. | ||
* | | Fix setting/setting/viewing metadata that contains unicode or other special ↵ | 2015-08-11 | |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | characters, when in a non-unicode locale. Oh boy, not again. So, another place that the filesystem encoding needs to be applied. Yay. In passing, I changed decodeBS so if a NUL is embedded in the input, the resulting FilePath doesn't get truncated at that NUL. This was needed to make prop_b64_roundtrips pass, and on reviewing the callers of decodeBS, I didn't see any where this wouldn't make sense. When a FilePath is used to operate on the filesystem, it'll get truncated at a NUL anyway, whereas if a String is being used for something else, it might conceivably have a NUL in it, and we wouldn't want it to get truncated when going through decodeBS. (NB: There may be a speed impact from this change.) | ||
* | | close | 2015-08-11 | |
| | | |||
| * | Added a comment: still broken, imho - possible fixes and workarounds | 2015-08-11 | |
|/ | |||
* | amazonka | 2015-08-11 | |
| | |||
* | comment | 2015-08-11 | |
| | |||
* | response | 2015-08-11 | |
| | |||
* | followup | 2015-08-11 | |
| | |||
* | response | 2015-08-11 | |
| | |||
* | metadata: Fix reversion introduced in 5.20150727 that caused display of ↵ | 2015-08-11 | |
| | | | | metadata to not work. | ||
* | remove my addition; I missed that bgilbert already said the same in a comment | 2015-08-11 | |
| | |||
* | followu | 2015-08-11 | |
| | |||
* | Merge branch 'master' of ssh://git-annex.branchable.com | 2015-08-11 | |
|\ | |||
* | | add link to gcsannex external special remote | 2015-08-11 | |
| | | |||
| * | Added a comment: any chance to get a native google drive annex support? | 2015-08-11 | |
| | | |||
| * | Added a comment: Linux-Windows repo | 2015-08-10 | |
| | | |||
| * | Initial report | 2015-08-09 | |
| | | |||
| * | Added a comment: External special remote | 2015-08-09 | |
| | | |||
| * | Added a comment: External special remote | 2015-08-09 | |
| | | |||
* | | remove obsolete tip | 2015-08-09 | |
|/ | |||
* | tip for git-annex-shell PATH issues | 2015-08-09 | |
| | |||
* | Merge branch 'master' of ssh://git-annex.branchable.com | 2015-08-09 | |
|\ | |||
* | | document a PATH issue | 2015-08-09 | |
| | | |||
| * | Added a comment | 2015-08-09 | |
| | | |||
* | | tyo | 2015-08-09 | |
|/ | |||
* | Improve Setup.hs file so that cabal copy --destdir works. Thanks, ↵ | 2015-08-09 | |
| | | | | Magnus_Therning. | ||
* | response | 2015-08-09 | |
| | |||
* | Revert "removed" | 2015-08-09 | |
| | | | | | | | This reverts commit e5546ac16dba167fcad7e9a7408e9726868cd3c3. This user will be banned if they make any further such apparently malicious or stupid changes. | ||
* | Added a comment | 2015-08-09 | |
| | |||
* | (no commit message) | 2015-08-09 | |
| | |||
* | Added a comment | 2015-08-09 | |
| | |||
* | (no commit message) | 2015-08-09 | |
| | |||
* | (no commit message) | 2015-08-08 | |
| | |||
* | (no commit message) | 2015-08-08 | |
| | |||
* | (no commit message) | 2015-08-08 | |
| | |||
* | removed | 2015-08-08 | |
| | |||
* | (no commit message) | 2015-08-06 | |
| | |||
* | (no commit message) | 2015-08-06 | |
| | |||
* | Merge branch 'master' of ssh://git-annex.branchable.com | 2015-08-06 | |
|\ | |||
| * | no haskell? | 2015-08-06 | |
| | | |||
* | | devblog | 2015-08-06 | |
|/ | |||
* | Merge branch 'master' of ssh://git-annex.branchable.com | 2015-08-06 | |
|\ | |||
* | | Added support for SHA3 hashed keys (in 8 varieties), when git-annex is built ↵ | 2015-08-06 | |
| | | | | | | | | | | | | | | | | using the cryptonite library. While cryptohash has SHA3 support, it has not been updated for the final version of the spec. Note that cryptonite has not been ported to all arches that cryptohash builds on yet. | ||
* | | promote comment to todo | 2015-08-06 | |
| | | |||
| * | Added a comment | 2015-08-06 | |
| | | |||
| * | removed | 2015-08-06 | |
| | |