comment
This commit is contained in:
parent
05ef86fcf3
commit
86428f6261
2 changed files with 20 additions and 0 deletions
|
@ -15,6 +15,9 @@ git-annex (6.20170521) UNRELEASED; urgency=medium
|
|||
an url to check if it exists. Some web servers take quite a long time
|
||||
to answer a HEAD request.
|
||||
* Windows: Win32 package has subsumed Win32-extras; update dependency.
|
||||
* Added annex-check-command configuration, which can be used to
|
||||
provide a shell command to check if a remote should be allowed to be
|
||||
used at all.
|
||||
|
||||
-- Joey Hess <id@joeyh.name> Sat, 17 Jun 2017 13:02:24 -0400
|
||||
|
||||
|
|
|
@ -0,0 +1,17 @@
|
|||
[[!comment format=mdwn
|
||||
username="joey"
|
||||
subject="""comment 3"""
|
||||
date="2017-08-17T16:06:44Z"
|
||||
content="""
|
||||
Another good reason to have a separate config is it should probably
|
||||
block `git annex sync` from pulling/pushing the remote. Cost does not
|
||||
affect pulling and pushing.
|
||||
|
||||
The two config settings `annex-ignore` and
|
||||
`annex-sync` are the non-dynamic ways to control this.
|
||||
So perhaps the way that annex-cost-command is the dynamic form of
|
||||
annex-cost, there ought to be annex-ignore-command and annex-sync-command.
|
||||
|
||||
That also allows for situations like a network where you want git-annex
|
||||
sync to only push the git repository but not annexed contents.
|
||||
"""]]
|
Loading…
Reference in a new issue