| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Avoid git reset here too, so I no longer need to care that it's much more
expensive than seems wise (but I asked the git list about that anyway).
It's not necessary to reset the staged file content from the index, as
the `git add` of the the symlink will replace it anyway.
`git commit` of unlocked files is still slow, since git still has to shove
their entire content into the index, only to have it be thrown away. So it's
still better to use `git annex add`
|
| |
|
|
|
| |
Previously, lock would skip files that had staged changes, but that is
counterintuitive, I think.
|
| |
|
|
| |
reset`, and only running `git checkout` once, even when many files are being locked.
|
| | |
|
| |
|
|
| |
Introduced in 43f0a666f0f6cc152a2b778921831d6d7daedcaf
|
| | |
|
| |
|
|
|
| |
Display the name of the remote being checked, with "." for the current
remote, echoing the way describe takes that to change its description.
|
| |
|
|
| |
list available remotes in case user wanted to use or change one of them
|
| | |
|
| |
|
|
|
| |
Otherwise, the user sees only a rsync protocol error message and then
git-annex's less specific failure message.
|
| |
|
|
|
| |
Just more golfing.. I am pretty sure something in a library somewhere can
do this, but I have been unable to find it.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
This way, individual words as entered on the command line are available
to commands.
|
| |
|
|
| |
the filename affects the key name.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
git when a remote's path contains a symlink. Closes: #621386
This was a real PITA to fix, since location logs can be staged in
both the current repo, as well as in local remote's repos, in
which case the cwd will not be in the repo. And git add needs different
params in both cases, when absolute paths are not used.
In passing, git annex fsck now stages location log fixes.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Since the queue is flushed in between subcommand actions being run,
there should be no issues with actions that expect to queue up some stuff
and have it run after they do other stuff. So I didn't have to audit for
such assumptions.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
Conflicts:
debian/changelog
|
| | |
| |
| |
| | |
permissions.
|
| |/ |
|
| |
|
|
| |
--fast. This assumes that location tracking information is correct, rather than contacting the remote for every file.
|
| |
|
|
| |
Drop old Remotes.hs, now unused!
|
| | |
|
| |
|
|
| |
only move and map still to convert
|
| | |
|
| |
|
|
| |
that can be used for free space checking.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
already present in .git/annex/objects.
For example, this could happen if using SHA1 and a file with content
"foo" were added to that backend. Then a file with "content" foo were
migrated from the WORM backend.
Assume that, if a backend assigned the same key, the already annexed
content must be the same. So, the "old" content can be reused.
|
| |
|
|
| |
temp files are always assumed to be unused, in either mode
|
| |
|
|
|
|
|
|
|
|
| |
Add --fast flag, that can enable less expensive, but also less thurough versions of some commands.
* Add --fast flag, that can enable less expensive, but also less thurough
versions of some commands.
* fsck: In fast mode, avoid checking checksums.
* unused: In fast mode, just show all existing temp files as unused,
and avoid expensive scan for other unused content.
|
| |
|
|
|
|
|
|
| |
Free space checking is now done, for transfers of data for keys that have free space metadata.
(Notably, not for SHA* keys generated with git-annex 0.24 or earlier.)
The code is believed to work on Linux, FreeBSD, and OSX; check compile-time
messages to see if it is not enabled for your OS.
|
| | |
|
| | |
|
Joey Hess