| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
I left status working in direct mode, although it doesn't show correct
stats for known annex keys.
|
|
|
|
| |
repository.
|
|
|
|
|
| |
Needs work to deal with directory renames better; otherwise seems to
basically work.
|
| |
|
|
|
|
|
|
| |
* SHA*E backends: Exclude non-alphanumeric characters from extensions.
* migrate: Remove leading \ in SHA* checksums, and non-alphanumerics
from extensions of SHA*E keys.
|
|
|
|
|
|
|
|
| |
* Bugfix: Remove leading \ from checksums output by sha*sum commands,
when the filename contains \ or a newline. Closes: #696384
* fsck: Still accept checksums with a leading \ as valid, now that
above bug is fixed.
* migrate: Remove leading \ in checksums
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The newline after the filename was included in it.
This was generally benign -- mostly these filenames are just displayed,
and the newline didn't matter.
But in the assistant, it caused unexpected dropping of preferred
content.
A characteristic of this bug is that the drop was displayed like this:
drop some_file
ok
|
|\ |
|
| | |
|
|\|
| |
| |
| |
| |
| | |
Conflicts:
debian/changelog
doc/design/assistant/desymlink.mdwn
|
| | |
|
|/ |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This got broken when I optimised reconnecting with remotes, to not do a
full scan if the remote was not diverged.
|
| |
|
|
|
|
|
|
|
| |
* get/copy --auto: Transfer data even if it would exceed numcopies,
when preferred content settings want it.
* drop --auto: Fix dropping content when there are no preferred content
settings.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
livedrive.com. Needs DAV version 0.3.
|
|
|
|
| |
currently-supported AWS regions.
|
| |
|
|
|
|
| |
See http://git-annex.branchable.com/forum/dot_git_slash_annex_slash_tmp/
|
|
|
|
|
|
|
|
|
|
| |
There are two reasons to to so. First, it allows not building with
WITH_OLD_SSH, and using ssh connection caching.
Second, per
http://git-annex.branchable.com/bugs/OSX_app_issues/#comment-3bdbc400a7c87c5cbc16e5aab5a52ac3
ssh can fail when run from the standalone build, due to library
incompatabilities. Building in ssh will avoid this.
|
| |
|
|
|
|
|
|
|
|
| |
It was doubly broken; both missing a slash, and containing
"runshell git-annex", while some parts of the code expected it to be a
simple path to a program. This appears to include the transfer queue
runner, and the code that starts a new assistant process when switching to
another repository in the webapp.
|
|
|
|
| |
one-click enabling of the repository.
|
| |
|
|
|
|
|
|
| |
variables before running the system web browser.
Should fix a crash reported on OSX.
|
|
|
|
| |
remotes.
|
|
|
|
| |
subdirectories. Could affect various parts of git-annex.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Old versions have an insufficiently generic definition of reader,
which only works on ReaderT and not on newtypes made of it, or something
like that.
|
| |
|
| |
|
|
|
|
| |
to the repository, by setting embedcreds=yes|no when running initremote.
|
|
|
|
|
|
|
|
|
|
| |
too small chunksize was configured.
Ensure that each file has something written to it, even if the bytestring
chunk size is greater than the configured chunksize.
This means we may write a bit larger than the configured value, but only
when the configured value is very small; ie, < 8 kb.
|
|
|
|
|
|
|
|
|
| |
Files are now written to a tmp directory in the remote, and once all
chunks are written, etc, it's moved into the final place atomically.
For now, checkpresent still checks every single chunk of a file, because
the old method could leave partially transferred files with some chunks
present and others not.
|
| |
|
|
|
|
|
|
| |
Both the directory and webdav special remotes used to have to buffer
the whole file contents before it could be decrypted, as they read
from chunks. Now the chunks are streamed through gpg with no buffering.
|
| |
|
| |
|