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

Added a comment

Browse source
This commit is contained in:
amerlyq 2022-01-29 15:59:31 +00:00 • committed by admin
parent d9203f0691
commit f9558108cf
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/adb_creates_empty_commits_on_import__47__sync/comment_7_f1e37aa68778408629c53c09f0a0857f._comment Normal file
View file

@ -0,0 +1,16 @@
[[!comment format=mdwn
username="amerlyq"
avatar="http://cdn.libravatar.org/avatar/3d63c9f436b45570d45bd003e468cbd3"
subject="comment 7"
date="2022-01-29T15:59:31Z"
content="""
> * if I create a new repo and do \"export\" multiple times in a row into empty folder -- it works OK.
> * But on the next day when I'm trying to \"export\" again -- it reports error \"unsafe to overwrite file //failed\"
I somewhat narrowed down the issue.
Error \"unsafe to overwrite file\" only appears for plaint text files (and symlinks) committed to .git itself.
This error only appears after several exports and some time passes (still can't catch conditions).
Current hypothesis is that empty commits in history are related to these plain text files.
@joey, do you have any thoughts?
"""]]