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

followup

Browse source
This commit is contained in:
Joey Hess 2018-10-29 15:28:58 -04:00
parent 64a369a1e2
commit 0b52f95c05
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 22 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
doc/todo/copy_instead_of_rename_on_reinject/comment_1_8e1fefa8231cc93f0f1958e44d869c47._comment Normal file
View file

@ -0,0 +1,22 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2018-10-29T19:20:15Z"
content="""
The first word of the git-annex-reinject man page is "moves", so
I find it hard to believe users would be surprised that it does that.
(Also, "inject" suggests movement.)
I can't see this being anything but an option added to reinject, because
changing behavior to copying when it's been move *would* be surprising, and
could result in a lot of unwanted disk space being used or other problems
with some workflow that involves reinject.
I am doubtful that such an option is worth it given the way git-annex
reinject is usually used.
And if I were in your situation, which I have been, I'd just delete the symlinks
I moved by accident, check them back out in the other repository,
and then unannex the files and move them. Much easier than running reinject
with long paths into the other repository.
"""]]