forum/Workflow for adding filesgit-annexhttp://git-annex.branchable.com/forum/Workflow_for_adding_files/git-annexikiwiki2014-06-18T07:35:31Zcomment 1http://git-annex.branchable.com/forum/Workflow_for_adding_files/comment_1_a60dae97db827bc641d6256d1f382b5f/Frederik2014-05-15T00:57:23Z2014-05-15T00:57:23Z
Check the description for manual out on <a href="http://git-annex.branchable.com/preferred_content/standard_groups/">http://git-annex.branchable.com/preferred_content/standard_groups/</a>. I believe that's what you'll need.
comment 2http://git-annex.branchable.com/forum/Workflow_for_adding_files/comment_2_28dd15ac50f79fb07bacf8b8326c7edc/Florian2014-06-18T07:35:31Z2014-06-18T07:35:31Z
<p>Just to be sure I understood the topic, this would be achieved in putting the repo in the manual transfer group?</p>
<p>manual</p>
<p>This gives you nearly full manual control over what content is stored in the repository. This allows using the assistant without it trying to keep a local copy of every file. Instead, you can manually run git annex get, git annex drop, etc to manage content. Only content that is already present is wanted.</p>
<p>The exception to this manual control is that content that a client repository would not want is not wanted. So, files in archive directories are not wanted once their content has reached an archive repository.</p>
<p>present and ($client)</p>
<p>(Where $client is a copy of the preferred content expression used for clients.)
<<<</p>