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

comment

Browse source
This commit is contained in:
Joey Hess 2020-11-10 11:53:45 -04:00
parent 4c1eb28c40
commit 9e8eae20e2
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 16 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
doc/bugs/file_not_correctly_added/comment_10_07583ff86653cb262f84e307c2ffc797._comment Normal file
View file

@ -0,0 +1,16 @@
[[!comment format=mdwn
username="joey"
subject="""comment 10"""
date="2020-11-10T15:50:10Z"
content="""
So was myLargeFile.CR2 in fact an annex pointer file all along?
Anyway, I think it might be possible to avoid this confusing kind of
situation. If git-annex add sees an annex pointer file or symlink, it can
check if there's a location log file for it. Normally there always is. If
not, that's a situation where some file from another annex is being added,
and it can either warn, or refuse to proceed.
This will only really be worth doing if git-annex smudge --clean can also
do it, so if git add is used it does the same check.
"""]]