git-annex-gpl - git-annex without the AGPL

	Commit message (Collapse)	Author	Age
*	remove old closed bugs and todo items to speed up wiki updates and reduce size	Joey Hess	2017-09-29
\| \| \| \| \| \| \| \| \|	Remove closed bugs and todos that were last edited or commented before 2017. Command line used: for f in $(grep -l '\|done\]\]' -- .mdwn); do d="$(echo "$f" \| sed 's/.mdwn$//')"; if [ -z "$(git log --since=01-01-2017 --pretty=oneline -- "$f")" -a -z "$(git log --since=01-01-2017 --pretty=oneline -- "$d")" ]; then git rm -- "./$f" ; git rm -rf "./$d"; fi; done for f in $(grep -l '\[\[done\]\]' -- .mdwn); do d="$(echo "$f" \| sed 's/.mdwn$//')"; if [ -z "$(git log --since=01-01-2017 --pretty=oneline -- "$f")" -a -z "$(git log --since=01-01-2017 --pretty=oneline -- "$d")" ]; then git rm -- "./$f" ; git rm -rf "./$d"; fi; done
*	Added a comment	christoph.schober@b8a66d38d9dfeeb6d7cd83888079d5870014ad7a	2016-02-18
\|
*	fsck: Populate unlocked files in v6 repositories whose content is present in ↵	Joey Hess	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 ↵	Joey Hess	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.