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

comment

Browse source
This commit is contained in:
Joey Hess 2018-07-11 15:54:18 -04:00
parent 32df7fca23
commit 7f2e76c462
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 25 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

25
doc/bugs/Importing__95__Commands__95__Destructive__95__by__95__default/comment_7_c8a0a64aa4253ba2eea525ce9fc67d4f._comment Normal file
View file

@ -0,0 +1,25 @@
[[!comment format=mdwn
username="joey"
subject="""comment 7"""
date="2018-07-11T19:41:15Z"
content="""
Seems to me that the documentation of git-annex import, git-annex reinject,
and git-annex setkey is clear, that these commands all move content into the
annex.
If you don't want it to move, you can always make a copy of the file first,
and run the command on the copy. But git-annex is about managing large
files, and making a second local copy of a large file would be surprising
behavior if the user didn't explicitly ask for it.
When you set up a remote somewhere, and ask git-annex to ensure numcopies
is 2+, it is *then* eager to preserve multiple copies, because it's been
given a way to do so, and been told to. It's not eager by default though.
Given that people get confused with the existing number of options to
git-annex import, I'm reluctant to add more to it, especially if the same
behavior as the suggested options can be obtained by running `cp` first.
I still don't fully understand what your proposed options are supposed
to do..
"""]]