2015-03-23 19:36:10 +00:00
|
|
|
# NAME
|
|
|
|
|
2015-07-09 23:03:21 +00:00
|
|
|
git-annex drop - remove content of files from repository
|
2015-03-23 19:36:10 +00:00
|
|
|
|
|
|
|
# SYNOPSIS
|
|
|
|
|
|
|
|
git annex drop `[path ...]`
|
|
|
|
|
|
|
|
# DESCRIPTION
|
|
|
|
|
|
|
|
Drops the content of annexed files from this repository, when
|
|
|
|
possible.
|
|
|
|
|
|
|
|
git-annex will refuse to drop content if it cannot verify it is
|
|
|
|
safe to do so.
|
|
|
|
|
|
|
|
# OPTIONS
|
|
|
|
|
|
|
|
* `--from=remote`
|
|
|
|
|
|
|
|
Rather than dropping the content of files in the local repository,
|
2015-05-30 14:54:14 +00:00
|
|
|
this option can specify a remote from which the files'
|
2015-03-23 19:36:10 +00:00
|
|
|
contents should be removed.
|
|
|
|
|
2015-03-25 21:06:14 +00:00
|
|
|
* `--auto`
|
|
|
|
|
|
|
|
Rather than trying to drop all specified files, drop only files that
|
|
|
|
are not preferred content of the repository.
|
|
|
|
See [[git-annex-preferred-content]](1)
|
|
|
|
|
2015-03-23 19:36:10 +00:00
|
|
|
* `--force`
|
|
|
|
|
|
|
|
Use this option with care! It bypasses safety checks, and forces
|
|
|
|
git-annex to delete the content of the specified files, even from
|
|
|
|
the last repository that is storing their content. Data loss can
|
|
|
|
result from using this option.
|
|
|
|
|
2018-04-04 03:12:04 +00:00
|
|
|
* `--all` `-A`
|
2015-05-12 17:00:06 +00:00
|
|
|
|
|
|
|
Rather than specifying a filename or path to drop, this option can be
|
|
|
|
used to drop all available versions of all files.
|
|
|
|
|
|
|
|
This is the default behavior when running git-annex drop in a bare repository.
|
|
|
|
|
--branch, stage 1
Added --branch option to copy, drop, fsck, get, metadata, mirror, move, and
whereis commands. This option makes git-annex operate on files that are
included in a specified branch (or other treeish).
The names of the files from the branch that are being operated on are not
displayed yet; only the keys. Displaying the filenames will need changes
to every affected command.
Also, note that --branch can be specified repeatedly. This is not really
documented, but seemed worth supporting, especially since we may later want
the ability to operate on all branches matching a refspec. However, when
operating on two branches that contain the same key, that key will be
operated on twice.
2016-07-20 16:05:22 +00:00
|
|
|
Note that this bypasses checking the .gitattributes annex.numcopies
|
|
|
|
setting.
|
|
|
|
|
|
|
|
* `--branch=ref`
|
|
|
|
|
|
|
|
Drop files in the specified branch or treeish.
|
|
|
|
|
|
|
|
Note that this bypasses checking the .gitattributes annex.numcopies
|
|
|
|
setting.
|
|
|
|
|
2015-05-12 17:00:06 +00:00
|
|
|
* `--unused`
|
|
|
|
|
|
|
|
Drop files found by last run of git-annex unused.
|
|
|
|
|
--branch, stage 1
Added --branch option to copy, drop, fsck, get, metadata, mirror, move, and
whereis commands. This option makes git-annex operate on files that are
included in a specified branch (or other treeish).
The names of the files from the branch that are being operated on are not
displayed yet; only the keys. Displaying the filenames will need changes
to every affected command.
Also, note that --branch can be specified repeatedly. This is not really
documented, but seemed worth supporting, especially since we may later want
the ability to operate on all branches matching a refspec. However, when
operating on two branches that contain the same key, that key will be
operated on twice.
2016-07-20 16:05:22 +00:00
|
|
|
Note that this bypasses checking the .gitattributes annex.numcopies
|
|
|
|
setting.
|
|
|
|
|
2015-05-12 17:00:06 +00:00
|
|
|
* `--key=keyname`
|
|
|
|
|
|
|
|
Use this option to drop a specified key.
|
|
|
|
|
--branch, stage 1
Added --branch option to copy, drop, fsck, get, metadata, mirror, move, and
whereis commands. This option makes git-annex operate on files that are
included in a specified branch (or other treeish).
The names of the files from the branch that are being operated on are not
displayed yet; only the keys. Displaying the filenames will need changes
to every affected command.
Also, note that --branch can be specified repeatedly. This is not really
documented, but seemed worth supporting, especially since we may later want
the ability to operate on all branches matching a refspec. However, when
operating on two branches that contain the same key, that key will be
operated on twice.
2016-07-20 16:05:22 +00:00
|
|
|
Note that this bypasses checking the .gitattributes annex.numcopies
|
|
|
|
setting.
|
|
|
|
|
2015-03-23 19:36:10 +00:00
|
|
|
* file matching options
|
|
|
|
|
|
|
|
The [[git-annex-matching-options]](1)
|
|
|
|
can be used to specify files to drop.
|
|
|
|
|
2015-11-04 21:13:20 +00:00
|
|
|
* `--jobs=N` `-JN`
|
|
|
|
|
|
|
|
Runs multiple drop jobs in parallel. This is particularly useful
|
|
|
|
when git-annex has to contact remotes to check if it can drop files.
|
|
|
|
For example: `-J4`
|
|
|
|
|
2019-05-10 17:24:31 +00:00
|
|
|
Setting this to "cpus" will run one job per CPU core.
|
|
|
|
|
2016-07-06 15:54:46 +00:00
|
|
|
* `--batch`
|
|
|
|
|
|
|
|
Enables batch mode, in which lines containing names of files to drop
|
|
|
|
are read from stdin.
|
|
|
|
|
make --batch honor matching options
When --batch is used with matching options like --in, --metadata, etc, only
operate on the provided files when they match those options. Otherwise, a
blank line is output in the batch protocol.
Affected commands: find, add, whereis, drop, copy, move, get
In the case of find, the documentation for --batch already said it honored
the matching options. The docs for the rest didn't, but it makes sense to
have them honor them. While this is a behavior change, why specify the
matching options with --batch if you didn't want them to apply?
Note that the batch output for all of the affected commands could
already output a blank line in other cases, so batch users should
already be prepared to deal with it.
git-annex metadata didn't seem worth making support the matching options,
since all it does is output metadata or set metadata, the use cases for
using it in combination with the martching options seem small. Made it
refuse to run when they're combined, leaving open the possibility for later
support if a use case develops.
This commit was sponsored by Brett Eisenberg on Patreon.
2018-08-08 16:03:30 +00:00
|
|
|
As each specified file is processed, the usual output is
|
|
|
|
displayed. If a file's content is not present, or it does not
|
|
|
|
match specified matching options, or it is not an annexed file,
|
|
|
|
a blank line is output in response instead.
|
|
|
|
|
added -z
Added -z option to git-annex commands that use --batch, useful for
supporting filenames containing newlines.
It only controls input to --batch, the output will still be line delimited
unless --json or etc is used to get some other output. While git often
makes -z affect both input and output, I don't like trying them together,
and making it affect output would have been a significant complication,
and also git-annex output is generally not intended to be machine parsed,
unless using --json or a format option.
Commands that take pairs like "file key" still separate them with a space
in --batch mode. All such commands take care to support filenames with
spaces when parsing that, so there was no need to change it, and it would
have needed significant changes to the batch machinery to separate tose
with a null.
To make fromkey and registerurl support -z, I had to give them a --batch
option. The implicit batch mode they enter when not provided with input
parameters does not support -z as that would have complicated option
parsing. Seemed better to move these toward using the same --batch as
everything else, though the implicit batch mode can still be used.
This commit was sponsored by Ole-Morten Duesund on Patreon.
2018-09-20 20:09:21 +00:00
|
|
|
* `-z`
|
|
|
|
|
|
|
|
Makes the `--batch` input be delimited by nulls instead of the usual
|
|
|
|
newlines.
|
|
|
|
|
2016-07-06 15:54:46 +00:00
|
|
|
* `--json`
|
|
|
|
|
|
|
|
Enable JSON output. This is intended to be parsed by programs that use
|
|
|
|
git-annex. Each line of output is a JSON object.
|
|
|
|
|
2018-02-19 18:28:17 +00:00
|
|
|
* `--json-error-messages`
|
|
|
|
|
2018-02-19 19:33:59 +00:00
|
|
|
Messages that would normally be output to standard error are included in
|
|
|
|
the json instead.
|
2018-02-19 18:28:17 +00:00
|
|
|
|
2015-03-23 19:36:10 +00:00
|
|
|
# SEE ALSO
|
|
|
|
|
|
|
|
[[git-annex]](1)
|
|
|
|
|
2015-05-29 16:12:55 +00:00
|
|
|
[[git-annex-get]](1)
|
|
|
|
|
|
|
|
[[git-annex-move]](1)
|
|
|
|
|
|
|
|
[[git-annex-copy]](1)
|
|
|
|
|
2015-03-23 19:36:10 +00:00
|
|
|
# AUTHOR
|
|
|
|
|
|
|
|
Joey Hess <id@joeyh.name>
|
|
|
|
|
|
|
|
Warning: Automatically converted into a man page by mdwn2man. Edit with care.
|