Added a comment

This commit is contained in:
david.j.buckmaster@984ff2704feacab53415ac5647206517d18f88f8 2019-02-24 01:20:15 +00:00 committed by admin
parent 89ee156059
commit 3f450e5271

View file

@ -0,0 +1,24 @@
[[!comment format=mdwn
username="david.j.buckmaster@984ff2704feacab53415ac5647206517d18f88f8"
nickname="david.j.buckmaster"
avatar="http://cdn.libravatar.org/avatar/1650cdf23a0999fd0e03650e20c90ee7"
subject="comment 1"
date="2019-02-24T01:20:14Z"
content="""
I guess the issue here isn't specifically the truncation, but rather that annexed content isn't confirmed when committing an rm.
set -x && \
mkdir tmp && cd tmp && \
git init && \
git-annex init --version 7 base && \
git-annex config --set annex.thin true && \
\
echo \"bar\">foo && cat foo && git-annex add foo && ls -l && git-annex sync && git-annex unlock foo && git-annex sync && \
echo \"barbar\">foo && cat foo && rm foo && git-annex sync && \
\
echo \"bar\">ffoo && cat ffoo && git-annex add ffoo && git-annex sync && cat ffoo
This results in ffoo containing the text \"barbar\" rather than \"bar\" (symlink to foo's last committed content), and unlocking ffoo after this leads to a pointer file instead of hardlink (and git-annex info ffoo shows present: false).
I'm new to this, so apologies if I'm doing something stupid.
"""]]