mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Merge branch 'master' of ssh://git-annex.branchable.com

Browse source
This commit is contained in:
Joey Hess 2013-10-28 13:47:42 -04:00
commit 16045d15fe
2 changed files with 30 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

20
doc/forum/known_and_local_annex_keys/comment_1_3cb4828dc7116e4cf49e119f055ae9a3._comment Normal file
View file

@ -0,0 +1,20 @@
[[!comment format=mdwn
username="http://joeyh.name/"
ip="209.250.56.47"
subject="comment 1"
date="2013-10-28T16:56:20Z"
content="""
I think you're stressing way too much about a number.
It's quite possible for the known and local key counts to diverge while no data is missing. For example:
<pre>
joey@darkstar:~/tmp/test>touch foo
joey@darkstar:~/tmp/test>touch bar
joey@darkstar:~/tmp/test>git annex add foo bar
local annex keys: 1
known annex keys: 2
</pre>
"""]]

10
doc/todo/whishlist:_git_annex_drop_--dry-run/comment_1_20ecfa8ffa52c238d21b904076ac69a2._comment Normal file
View file

@ -0,0 +1,10 @@
[[!comment format=mdwn
username="http://joeyh.name/"
ip="209.250.56.47"
subject="comment 1"
date="2013-10-28T17:11:04Z"
content="""
It would be nice, but it adds quite a lot of complexity to have a --dry-run, and if I add it to just drop, the next bug is going to ask for get to have it..
I feel that the right approach is to add a --wanted, which could then be used with find to find files that are and are not wanted, according to the preferred content settings. To see what it would want to get: `git annex find --wanted --not --in .` To see what it would want to drop: `git annex find --not --wanted --in .`
"""]]