| Commit message (Collapse) | Author | Age |
... | |
| |
| |
| |
| | |
the setting of HOME. Instead, copy msysgit's ssh into PATH.
|
| |
| |
| |
| | |
when running fsck in a read-only repository. Closes: #698559 (fsck can still need to write to the repository if it find problems, but a successful fsck can be done read-only)
|
| | |
|
| | |
|
| |
| |
| |
| | |
symlinks when downloading from ftp.
|
| | |
|
| | |
|
| |
| |
| |
| | |
Tested it builds, but have not run it yet.
|
| | |
|
| |
| |
| |
| | |
doesn't exist. It will now continue to other files specified after that on the command line, and only error out at the end.
|
| |
| |
| |
| | |
--clean-duplicates mode, verify that enough copies of its content still exist.
|
| |
| |
| |
| | |
14.12.3 while still being compatable with 4.14.2. Thanks, silvio.
|
| |
| |
| |
| | |
or conflicting with something in the work tree.
|
| |
| |
| |
| | |
git 1.8.4 or newer.)
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
cannot handle upper-case bucket names. git-annex now converts them to lower case automatically.
For example, it failed to get files from a bucket named S3.
Also fixes `git annex initremote UPPERCASE type=S3`, which failed with the
new aws library, with a signing error message.
|
| | |
|
| |
| |
| |
| | |
the bucket already exists.
|
| |
| |
| |
| | |
(endpoint, port, storage class)
|
| | |
|
| |
| |
| |
| |
| |
| | |
Jessie.
466 lines of compat cruft deleted!
|
| | |
|
| |
| |
| |
| | |
To debug a bug report, but generally useful.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
git-annex
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
The setDifferences that got added to initialize turns out to make a git
commit, and before ensureCommit has been used. Thus, repo init can fail
when the system has a broken hostname etc.
Move the ensureCommit to the very first thing to avoid this kind of breakage.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Also refactored some code to reduce duplication.
|
| |
| |
| |
| | |
annex.diskreserve limit.
|
| |
| |
| |
| | |
repo does not have a copy of the content, preserve the bad content in .git/annex/bad/ to avoid further data loss.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
special remote. This was a reversion caused by the relative path changes in 5.20150113.
The directory special remote was not affected in its normal configuration,
since annex-directory is an absolute path normally. But it could fail
when a relative path was used.
The git remote was affected even when an absolute path to it was used in
.git/config, since git-annex now converts all such paths to relative.
|
| |
| |
| |
| |
| |
| |
| | |
getting content if the disk is too full.
We can't check if there's enough disk space to download the content,
but we *can* check if there's certainly not enough!
|
|\|
| |
| |
| |
| | |
Conflicts:
debian/changelog
|
| |
| |
| |
| |
| |
| | |
Since we started using this for git repos, when a remote was on another
drive, it resulted in a bogus relative path to it being used by git-annex,
which didn't work.
|
| | |
|
| |
| |
| |
| | |
where the menu file is treated as a git-annex program.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
specified directory.
This is a nearly free feature; it piggybacks on the location log lookups
done for the numcopies stats. So, the only extra overhead is updating
the map of repository sizes.
However, I had to switch to Data.Map.Strict, which needs containers 0.5.
If backporting to wheezy, will probably need to revert this commit.
|
|/
|
|
|
|
|
|
|
|
|
| |
This works, and seems fairly robust. Clean get of 20 files at -J3. At -J10,
there are some messages about ssh multiplexing, probably due to a race
spinning up the ssh connection cacher. But, it manages to get all the files
ok regardless.
The progress bars are a scrambled mess though, due to bugs in
ascii-progress, which I've already filed. Particularly this one:
https://github.com/yamadapc/haskell-ascii-progress/issues/8
|
|
|
|
|
| |
Otherwise, if there's a file in the repo with a name matching the ref,
git could get confused and the merge not work.
|
|
|
|
|
| |
I had some cargo culting in there that used the wrong type, so it failed
to parse old logs, and overwrote them with the new log.
|
| |
|