| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| | |
|
| |
|
|
| |
it to the configuration for any ssh remotes previously created by the assistant. This avoids repeated prompts by ssh if the host key changes, instead syncing with such a remote will fail. Closes: #732602
|
| |
|
|
| |
follow symlinks to other directories, and add their contents to the annex.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Batch detection is heuristic, so can sometimes fail. I observed one such
failure while starting up in a repository with 87000 files. After the first
several batches of ~5000 files, it fell out of batch mode, and never
re-entered it, and so made many more commits of a few files at a time
than necessary.
So, let's always use batch mode when in the startup scan. This avoids the
heuristic there, at least.
There is clearly also room to improve the heuristic. Possibly 10 files is
too high a bar to be found during a commit, on a system that can commit
quickly.
|
| |
|
|
| |
use it, to remove dependence on the host glibc.
|
| | |
|
| |
|
|
| |
directory in PATH as an alternative installation method, and will use readlink to find where the build was unpacked.
|
| |
|
|
|
| |
find --format: Added hashdirlower, hashdirmixed, keyname, and mtime format
variables.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
pulled from a remote. A bug prevented the files from being updated in the work tree, and this caused the modification to be reverted.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Fixes a test case I received where a corrupted repo was repaired, but the
git-annex branch was not. The root of the problem was that the
MissingObject returned by the repair code was not necessarily a complete
set of all objects that might have been deleted during the repair.
So, stop trying to return that at all, and instead make the index file
checking code explicitly verify that each object the index uses is present.
|
| | |
|
| |
|
|
|
|
| |
earlier fix to bad behavior in Chromium.
Browsers are crap.
|
| | |
|
| |
|
|
|
| |
Works around yesod-static path bug on windows.
https://github.com/yesodweb/yesod/issues/626
|
| |
|
|
|
|
|
|
|
| |
importing
Previous test did not notice if there is a dangling symlink.
Also, if a directory exists with the same name as the imported file, that
cannot work, so don't let --force have an effect.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Note that the hash backends were made to stop printing a (checksum..)
message as part of this, since it showed up without a file when deciding
whether to act on a file. Should have probably removed that message a while
ago anyway, I suppose.
|
| |
|
|
| |
find DNS server, since there is no resolv.conf.
|
| |
|
|
|
|
| |
Use new url when making new remotes.
Transparently rewrite old url to new for existing remotes.
|
| |
|
|
| |
always try to get the file from the remote.
|
| |
|
|
| |
hashDirMixed. Closes: #731142
|
| |
|
|
| |
through 5.20131127.
|
| | |
|
| |
|
|
| |
commands are available.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
the full contents of files in the tree.
The assistant's commit code also always avoids git commit, for simplicity.
Indirect mode sync still does a git commit -a to catch unstaged changes.
Note that this means that direct mode sync no longer runs the pre-commit
hook or any other hooks git commit might call. The git annex pre-commit
hook action for direct mode is however explicitly run. (The assistant
already ran git commit with hooks disabled, so no change there.)
|
| | |
|
| |
|
|
| |
to set core.bare=false.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
mode repo, so the upgrade was performed repeatedly, slowing commands down.
|
| | |
|
| |
|
|
| |
interface compared with the old version.
|
| |
|
|
|
|
|
| |
they use the new guarded direct mode.
git treats eg ~/annex as a bare git repository located in ~/.annex/.git
if ~/annex/.git/config has core.bare=true.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Not yet wired up to restart the assistant on upgrade; that needs careful
sanity checking to wait until the upgrade is done before restarting.
Used the DirWatcher here, so it gets events for any changes to the
directory containing the program file. (But not subdirs.) This is necessary
in order to detect when the file is renamed as part of the upgrade, which
an inotify on a single file would not detect. (Also, I have DirWatcher code,
but not FileWatcher code.)
Note that upgrades that remove or rename a whole directory tree containing
the executable will *not* trigger this code. So eg, deleting and replacing
the whole standalone tarball dir tree won't work -- but untarring it
over top will. So should dpkg package upgrades.
Added programPath, using a new GHC feature to find the full path to the
executable. The fallback code for old GHC or unsupported OS is less good;
its worst failure mode would be either failing to find the program, and so
not checking for upgrades, or finding a git-annex that's in PATH, but is
not the one running.
This commit was sponsored by John Roepke.
|
| | |
|
| |
|
|
|
|
|
|
| |
In 0.9, -v shows version, rather than controlling verbosity.
Still need to port to 0.9, this just avoids massively confusing addurl when
quvi prints its version and exits successfully, on urls that it cannot be
used with.
|
Joey Hess