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 2021-01-29 14:44:03 -04:00
parent b92963c766
commit 93e5eb3378
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 17 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
doc/bugs/git_annex_import_is_dangerous_if_you_have_unused_objects/comment_6_6def3c88ced56753e4b12ce221d33769._comment Normal file
View file

@ -0,0 +1,17 @@
[[!comment format=mdwn
username="joey"
subject="""comment 6"""
date="2021-01-29T18:38:41Z"
content="""
To the extent that this is a bug in git-annex import, it's solved
by using the new feature of importing a tree from a directory special
remote. When used that way, there's no --deduplicate or --clean-duplicates
option that causes this problem. Instead it makes git commits tracking the
content of the remote directory, and as long as you merge that remote into
your master branch, the original filename will be preserved in git.
So once [[todo/remove_legacy_import_directory_interface]] happens, I
guess this could be considered fixed, to the extent it's a bug in git-annex
at all and not with using `git reset --hard` as I showed could lead to the
same thing in vanilla git.
"""]]