![]() Note that it does not check remotes to verify that the copies still exist. Matches only files that git-annex believes to have the specified number of copies, or more. Then you could configure your laptop to prefer to not retain those files, like this: exclude=*/archive/* While −−include=glob and −−exclude=glob match files relative to the current directory, preferred content expressions always match files relative to the top of the git repository.įor example, suppose you put files into archive directories when you’re done with them. If it doesn’t, the repository wants to drop its content (if there are enough copies elsewhere to allow removing it). If a file matches, the repository wants to store its content. The idea is that you write an expression that files are matched against. For example:Įxclude=archive/* and (include=*.mp3 or smallerthan=1mb) Preferred content expressions use a similar syntax to the git-annex−matching− options(1), without the dashes. A repository’s required content can be configured using git annex vicfg or git annex required. On the other hand, required content settings are enforced git annex drop will refuse to drop a file if doing so would violate its required content settings. While preferred content expresses a preference, it can be overridden by simply using git annex drop. They are used by the −−auto option, by git annex sync −−content, and by the git-annex assistant. These settings can be configured using git annex vicfg or git annex wanted. ![]() ![]() Git-annex−preferred−content − which files are wanted in a repository DESCRIPTIONĮach repository has a preferred content setting, which specifies content that the repository wants to have present.
0 Comments
Leave a Reply. |