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

show how this is not specific to git-annex at all

Browse source
This commit is contained in:
Joey Hess 2017-03-02 17:24:49 -04:00
parent 551848babd
commit 1e31a7c93a
No known key found for this signature in database
GPG key ID: C910D9222512E3C7
1 changed files with 31 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

31
doc/bugs/git_annex_import_is_dangerous_if_you_have_unused_objects/comment_1_9f9d5c18c27dfd33a5bf2c593ee65b58._comment Normal file
View file

@ -0,0 +1,31 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2017-03-02T21:20:02Z"
content="""
A simpler way to get to the same end result, without using git-annex
import:
mv ~/foo .
git annex add foo
git reset --hard
Now "foo" is only present in the git-annex object store, and we don't
know what its filename(s) were.
A way to get to the same end result, without using git-annex:
mv ~/foo .
git add foo
git reset --hard
Now "foo" is only present in the git object store, and we don't
know what its filename(s) were.
So, it's not `git-annex import`, or `git-annex add`, or `git add`
that is dangerous here. It's `git reset --hard`.
git will happily lose lots of data until you commit it. Once it's
committed, it's safe. That's the rule of thumb. Nothing much that git-annex
can do about that.
"""]]