Added a comment
This commit is contained in:
parent
fddf14600b
commit
1409a44f9c
1 changed files with 13 additions and 0 deletions
|
@ -0,0 +1,13 @@
|
||||||
|
[[!comment format=mdwn
|
||||||
|
username="richih@50508f31e0ee95720acd0120e16d6bdcad9d104b"
|
||||||
|
nickname="richih"
|
||||||
|
avatar="http://cdn.libravatar.org/avatar/499771047201f3eb29a462897b50a5f3"
|
||||||
|
subject="comment 3"
|
||||||
|
date="2018-04-10T15:49:35Z"
|
||||||
|
content="""
|
||||||
|
I agree with anarcat.
|
||||||
|
|
||||||
|
The core use case of git-annex is to maintain sets of known-good data. This function mainly relies on a directory structure, checksums, a defined minimum of copies, and tracking where they are. I would never have assumed that I would be able to get git-annex to go below the mincopies, at least not unless I was deep into the innards of git-annex and/or abusing --force or the like.
|
||||||
|
|
||||||
|
-- RichiH
|
||||||
|
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue