| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
direct mode.
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
avoiding use of it in such a locale.
Instead -J will behave as if it was built without concurrent-output support
in this situation. Ie, it will be mostly quiet, except when there's an
error.
Note that it's not a problem for a filename to contain invalid utf-8 when
in a utf-8 locale. That is handled ok by concurrent-output. It's only
displaying unicode characters in a non-unicode locale that doesn't work.
|
| |
|
|
|
| |
* checkpresentkey: Allow to be run without an explicit remote.
* checkpresentkey: Added --batch.
|
| |
|
|
|
|
| |
This lets readonly repos be used. If a repo is readonly, we can ignore the
keys database, because nothing that we can do will change the state of the
repo anyway.
|
| | |
|
| |
|
|
|
|
| |
instead of the default DNS-style access.
untested
|
| |
|
|
|
|
|
|
| |
temporary store location for a key. Thanks, wzhd.
That trailing slash is needed for legacy chunked mode, because it puts the
chunks in a subdir under the key. But, outside legacy chunked mode, it's BS
and it's amazing it worked at all with some webdav servers.
|
| |
|
|
| |
servers. Thanks, wzhd.
|
| |
|
|
| |
initializing in a subdirectory of a submodule and a submodule of a submodule.
|
| |
|
|
| |
without C libraries that may be hard to install.
|
| |
|
|
|
|
| |
I needed BUILDEROPTIONS to allow passing flags to stack build, but it also
lets me move the -j1 out of the normal build path, and to debian/rules
which has the goal of having a reproducible build
|
| |
|
|
| |
expression.
|
| |
|
|
| |
linked with libmagic.
|
| |
|
|
|
|
| |
expressions that make sense in its context.
So, not "standard" or "lackingcopies", etc.
|
| |
|
|
|
| |
This is particulary useful for v6 repositories, since the .gitattributes
configuration will apply in all clones of the repository.
|
| |
|
|
|
| |
Same as "not anything"; will be particularly useful in annex.largefiles
gitattributes.
|
| |
|
|
|
|
|
| |
removeDirectoryRecursive "." fails; need full path.
I think this is a reversion introduced in the relative path conversion, in
january of *last* year!
|
| |
|
|
| |
them to sometimes output side messages.
|
| |
|
|
| |
not matching annex.largefiles.
|
| |
|
|
| |
haskell programs.
|
| |
|
|
|
|
| |
Note that 4ba917a7a5f67e96c3848ae13c6eaa9eba6300c5 maligned FTP
incorrectly. The type checker didn't catch that bug because of the monad
instance for lists.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
of many preferred content expressions.
The type checker should have noticed this, but the changes to mapM
that make it accept any Traversable hid the fact that it was not being
passed a list at all. Thus, what should have returned an empty list most
of the time instead returned [""] which was treated as the name of the
associated file, with disasterout consequences.
When I have time, I should add a test case checking what sync --content
drops. I should also consider replacing mapM with one re-specialized to
lists.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
* Removed the webapp-secure build flag, rolling it into the webapp build
flag.
* Removed the quvi and tahoe build flags, which only adds aeson to
the core dependencies.
* Removed the feed build flag, which only adds feed to the core
dependencies.
Build flags have cost in both code complexity and also make Setup configure
have to work harder to find a usable set of build flags when some
dependencies are missing.
|
| |
|
|
| |
expression matches some data.
|
| |
|
|
| |
It added some instances I had also implemented.
|
| |
|
|
| |
of relying on gnome/kde stuff that is not stable.
|
| | |
|
| |
|
|
|
|
| |
When Config.setConfig runs, it throws away the old Repo and loads a new
one. So, add an action to adjust the Repo so that -c settings will persist
across that.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
(unless the file was added directly to git due to annex.largefiles configuration.)
(Also done by add --json and import --json)
|
| |
|
|
| |
Include added key in output.
|
| |
|
|
|
| |
This is particuarly important for commands with --batch output, which was
not always being flushed at an appropriate time.
|
| | |
|
| |
|
|
| |
rather than all together at the end.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
User-Agent: git-annex
|
| | |
|
Joey Hess