Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | comment | 2016-03-01 | |
| | |||
* | Added a comment | 2016-03-01 | |
| | |||
* | Added a comment | 2016-03-01 | |
| | |||
* | Added a comment: recent snapshot seems has fixed it | 2016-03-01 | |
| | |||
* | Added a comment: more info | 2016-03-01 | |
| | |||
* | moreinfo | 2016-03-01 | |
| | |||
* | Fix bug preventing moving files to/from a repository with annex.pidlock set. | 2016-03-01 | |
| | |||
* | Fix data loss that can occur when annex.pidlock is set in a repository. | 2016-03-01 | |
| | |||
* | comment | 2016-03-01 | |
| | |||
* | comment | 2016-03-01 | |
| | |||
* | reopen | 2016-03-01 | |
| | |||
* | comment | 2016-03-01 | |
| | |||
* | Added a comment: similar problem | 2016-03-01 | |
| | |||
* | initial whining | 2016-03-01 | |
| | |||
* | (no commit message) | 2016-03-01 | |
| | |||
* | (no commit message) | 2016-02-29 | |
| | |||
* | forgot to add this comment earlier | 2016-02-29 | |
| | |||
* | close bug and changelog | 2016-02-26 | |
| | | | | finished testing recent commits, and I did solve it | ||
* | update | 2016-02-26 | |
| | |||
* | bug | 2016-02-26 | |
| | |||
* | close | 2016-02-26 | |
| | |||
* | (no commit message) | 2016-02-26 | |
| | |||
* | (no commit message) | 2016-02-26 | |
| | |||
* | (no commit message) | 2016-02-24 | |
| | |||
* | todo | 2016-02-23 | |
| | |||
* | comment | 2016-02-23 | |
| | |||
* | added [[!meta author=yoh]] | 2016-02-23 | |
| | |||
* | (no commit message) | 2016-02-23 | |
| | |||
* | tag bugs that will be fixed when direct mode is removed | 2016-02-19 | |
| | |||
* | close | 2016-02-19 | |
| | |||
* | followup | 2016-02-19 | |
| | |||
* | Linux and OSX standalone builds put the bundled gpg last in PATH, so any ↵ | 2016-02-19 | |
| | | | | system gpg will be preferred over it. | ||
* | close | 2016-02-19 | |
| | |||
* | comment | 2016-02-19 | |
| | |||
* | Added a comment: 'git-annex semitrust' seems to solve the issue | 2016-02-18 | |
| | |||
* | Added a comment | 2016-02-18 | |
| | |||
* | Added a comment: repository marked as dead (!) | 2016-02-18 | |
| | |||
* | followup | 2016-02-17 | |
| | |||
* | followup | 2016-02-17 | |
| | |||
* | Add some more info to the bug report | 2016-02-17 | |
| | |||
* | Add bug report about failing tests when annex.backends is defined | 2016-02-17 | |
| | |||
* | (no commit message) | 2016-02-15 | |
| | |||
* | Added a comment | 2016-02-15 | |
| | |||
* | Merge branch 'master' of ssh://git-annex.branchable.com | 2016-02-14 | |
|\ | |||
* | | fsck: Populate unlocked files in v6 repositories whose content is present in ↵ | 2016-02-14 | |
| | | | | | | | | | | | | annex/objects but didn't reach the work tree. This also handles fixing up after f9dfeaf801da2e4d5879b3de5895dc3cef68a329 | ||
* | | Fix storing of filenames of v6 unlocked files when the filename is not ↵ | 2016-02-14 | |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | representable in the current locale. This is a mostly backwards compatable change. I broke backwards compatability in the case where a filename starts with double-quote. That seems likely to be very rare, and v6 unlocked files are a new feature anyway, and fsck needs to fix missing associated file mappings anyway. So, I decided that is good enough. The encoding used is to just show the String when it contains a problem character. While that adds some overhead to addAssociatedFile and removeAssociatedFile, those are not called very often. This approach has minimal decode overhead, because most filenames won't be encoded that way, and it only has to look for the leading double-quote to skip the expensive read. So, getAssociatedFiles remains fast. I did consider using ByteString instead, but getting a FilePath converted with all chars intact, even surrigates, is difficult, and it looks like instance PersistField ByteString uses Text, which I don't trust for problem encoded data. It would probably be slower too, and it would make the database less easy to inspect manually. | ||
| * | Added a comment | 2016-02-14 | |
| | | |||
* | | close | 2016-02-14 | |
|/ | |||
* | close | 2016-02-14 | |
| | |||
* | comment | 2016-02-14 | |
| |