diff options
author | Joey Hess <joeyh@joeyh.name> | 2015-06-16 20:30:48 -0400 |
---|---|---|
committer | Joey Hess <joeyh@joeyh.name> | 2015-06-16 20:30:48 -0400 |
commit | d688d6bbdc95d2a634071a2d3c34e18d07fddd40 (patch) | |
tree | 66ac8cacbb9106a8a4783ff87886ffcf9eff0ada /doc/preferred_content.mdwn | |
parent | 0d3c9ceec8884b7f40a3d956fe5be70b2b3381e1 (diff) |
reorg
Diffstat (limited to 'doc/preferred_content.mdwn')
-rw-r--r-- | doc/preferred_content.mdwn | 31 |
1 files changed, 17 insertions, 14 deletions
diff --git a/doc/preferred_content.mdwn b/doc/preferred_content.mdwn index e7a993fb0..33d327e9f 100644 --- a/doc/preferred_content.mdwn +++ b/doc/preferred_content.mdwn @@ -13,23 +13,13 @@ Each repository can have its own settings, and other repositories will try to honor those settings when interacting with it. (So there's no local `.git/config` for preferred content settings.) -[[!template id=note text=""" -### [[quickstart|standard_groups]] - -Rather than writing your own preferred content expression, you can use -several standard ones included in git-annex that are tuned to cover different -common use cases. - -You do this by putting a repository in a group, -and simply setting its preferred content to "standard" to match whatever -is standard for that group. See [[standard_groups]] for a list. -"""]] - The idea is that you write an expression that files are matched against. If a file matches, the repository wants to store its content. If it doesn't, the repository wants to drop its content (if there are enough copies elsewhere to allow removing it). +## finding preferred content + To check at the command line which files are matched by preferred content settings, you can use the --want-get and --want-drop options. @@ -38,6 +28,21 @@ files that `git annex get --auto` will want to get, and `git annex find --want-drop --in .` will find all the files that `git annex drop --auto` will want to drop. +## writing expressions + +[[!template id=note text=""" +### [[quickstart|standard_groups]] + +Rather than writing your own preferred content expression, you can use +several standard ones included in git-annex that are tuned to cover different +common use cases. + +You do this by putting a repository in a group, +and simply setting its preferred content to "standard" to match whatever +is standard for that group. See [[standard_groups]] for a list. +"""]] + + The expressions are very similar to the matching options documented on the [[git-annex-matching-options]] man page. At the command line, you can use those options in commands like this: @@ -52,8 +57,6 @@ So, just remove the dashes, basically. But, there are some differences between the command line options and expressions, so see the documentation below to get the full story. -## expressions - * `include=glob` and `exclude=glob` Match files to include, or exclude. |