Rather than specifying a filename or path to drop, this option can be used to drop all available versions of all files. Data loss can result from using this option. 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. See git-annex-preferred-content(1) -force Rather than trying to drop all specified files, drop only those that are not preferred content of the repository, and avoid trying to drop files when there are not enough other copies for the drop to be possible. Rather than dropping the content of files in the local repository, this option can specify a remote from which the files' contents should be removed.
(Use -force to override this check, or adjust numcopies.)ĭrop photo3.jpg (checking origin.) ok Options -from =remote Rather than dropping this file, try using: git annex move ExamplesĬould only verify the existence of 0 out of 1 necessary copies Paths of files or directories to drop can be specified. With no parameters, tries to drop all annexed files in the current directory. Usually this involves verifying that the content is stored in some other repository.Ĭontent that is required to be stored in the repository will not be dropped even if enough copies exist elsewhere. Git-annex will refuse to drop content if it cannot verify it is safe to do so. Git-annex drop - remove content of files from repository Synopsisĭrops the content of annexed files from this repository, when possible.
0 kommentar(er)
