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

Merge branch 'master' of ssh://git-annex.branchable.com

Browse source
This commit is contained in:
Joey Hess 2022-05-09 15:54:07 -04:00
commit 136ad17b94
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
3 changed files with 35 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
doc/bugs/git-annex-import_imports_outside_of_directory/comment_3_778e176a44aa57e9223aab1a45c931f3._comment Normal file
View file

@ -0,0 +1,19 @@
[[!comment format=mdwn
username="Ilya_Shlyakhter"
avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
subject="interaction of out-of-tree symlinks with exporttree"
date="2022-05-09T19:21:15Z"
content="""
One other scenario where the result might not be what users expect is the following: if a [[directory special remote|/special_remotes/directory]] is configured with both [[`importtree=yes`|git-annex-import]] and [[`exporttree=yes`|git-annex-export]], and the directory contains symlinks pointing outside the tree, then an import followed by an export will replace the symlink in the original directory with a copy of the content.
>a symlink that points outside the git repository, which is not something one often wants to check into a git repository
Such a symlink is already not something one often has :) But if one does, then the repo is likely for one's own usage, or for the usage by people with access to the shared filesystem where the link works, so adding the link to git as-is makes sense. Logically, it's likely that the out-of-tree link target represents some separate tree of files that you don't think of as part of the tree (or you'd have put them under the tree); if you did want to import them, you'd make a separate repo for them and import them as a submodule.
Also, what happens if the target tree of the out-of-tree link has a symlink back to the original tree -- could this cause infinite recursion?
The [[`git-annex-import` man page|git-annex-import]] says the command imports \"a tree of files\". It seems simplest if this description was always strictly true, regardless of what's in the tree. But if you decide to keep the current default, maybe clarify the web page?
Thanks again for all your work.
"""]]

8
doc/forum/Issues_with_non-sync_workflow/comment_4_a93d502253cf9f164fbcd23ca755db9d._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="lh"
avatar="http://cdn.libravatar.org/avatar/d31bade008d7da493d9bfb37d68fd825"
subject="comment 4"
date="2022-05-09T19:18:01Z"
content="""
Still curious about how `annex.alwayscommit=false` tracks modifications and whether mucking with a `git-annex` worktree could cause data loss with this option enabled.
"""]]

8
doc/todo/command_to___34__migrate__34___from_adjusted_mode/comment_2_845206fa688ed4786262fe6d82464d97._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="yarikoptic"
avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4"
subject="hm..."
date="2022-05-09T19:10:10Z"
content="""
I will need to figure out/try to reproduce how user ended up with .git/annex/objects in xxx/yyy instead of xx/yy layout...
"""]]