content: New command line way to view and configure a repository's preferred content settings.
This commit is contained in:
parent
e3c1586997
commit
b276857a7a
8 changed files with 70 additions and 8 deletions
|
@ -306,6 +306,14 @@ subdirectories).
|
|||
|
||||
Removes a repository from a group.
|
||||
|
||||
* content repository [expression]
|
||||
|
||||
When run with an expression, configures the content that is preferred
|
||||
to be held in the archive. See PREFERRED CONTENT below.
|
||||
|
||||
Without an expression, displays the current preferred content setting
|
||||
of the repository.
|
||||
|
||||
* vicfg
|
||||
|
||||
Opens EDITOR on a temp file containing most of the above configuration
|
||||
|
|
|
@ -6,10 +6,10 @@ control over which repositories prefer to have which content. Configuring
|
|||
this allows `git annex get --auto`, `git annex drop --auto`, etc to do
|
||||
smarter things.
|
||||
|
||||
Currently, preferred content settings can only be edited using `git
|
||||
annex vicfg`. Each repository can have its own settings, and other
|
||||
repositories may also try to honor those settings. So there's no local
|
||||
`.git/config` setting it.
|
||||
Preferred content settings can be edited using `git
|
||||
annex vicfg`, or viewed and set at the command line with `git annex content`.
|
||||
Each repository can have its own settings, and other repositories may also
|
||||
try to honor those settings. So there's no local `.git/config` setting it.
|
||||
|
||||
The idea is that you write an expression that files are matched against.
|
||||
If a file matches, it's preferred to have its content stored in the
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue