| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
|
|
| |
* add, addurl, import, importfeed: When in a v6 repository on a crippled
filesystem, add files unlocked.
* annex.addunlocked: New configuration setting, makes files always be
added unlocked. (v6 only)
|
|
|
|
|
|
|
|
|
|
|
| |
The problem with having the slashes unescaped is, it broke parsing, since
the parser takes the filename to get the part containing the key.
That particularly affected URL keys.
This makes the format be the same as symlinks point to, which keeps things
simple.
Existing pointer files will continue to work ok.
|
| |
|
| |
|
|
|
|
|
|
| |
Avoid possibly having the file open still when it gets deleted.
Needed on Windows, particularly.
|
|
|
|
|
| |
git-annex doesn't write \r, but it can be present due to line ending
conversions or perhaps user edits.
|
| |
|
|
|
|
|
| |
Pointer files were not being treated as annex content, so "git annex get"
didn't replace them with the object.
|
| |
|
|
|
|
| |
used by ghci wrapper script
|
| |
|
|
|
|
| |
direct mode.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
May be possible to install the library somehow, but it certainly won't be
available normally, and so cabal will fail to install magic.
|
| |
|
|\ |
|
| | |
|
| | |
|
|/ |
|
| |
|
| |
|
|\ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Use second ghc pass, not first.
|
| | |
|
|/ |
|
| |
|
|\ |
|
| | |
|
| |
| |
| |
| |
| |
| | |
annex/objects but didn't reach the work tree.
This also handles fixing up after f9dfeaf801da2e4d5879b3de5895dc3cef68a329
|
| |
| |
| |
| |
| | |
This also handles fixing up after the bad data written by
f9dfeaf801da2e4d5879b3de5895dc3cef68a329.
|
| |
| |
| |
| | |
When on crippled filesystem, or without annex.thin set.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
|
| | |
|
|/ |
|
| |
|
| |
|
|\ |
|
| | |
|