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

Browse source
This commit is contained in:
https://me.yahoo.com/a/x4ddlZwKw9O9IsCHmNZz7tSJn2h0H3vX#23f03 2017-12-07 18:37:29 +00:00 • committed by admin
parent 6bc4852d54
commit e8d95ee445
1 changed files with 38 additions and 36 deletions
Download patch file Download diff file Expand all files Collapse all files

8
doc/bugs/weird_bug_with_annex_unlock_with_annex.thin_true_about_hard_links.mdwn
View file

@ -20,14 +20,16 @@ Currently I have a repository that exhibits the problem:
git annex lock bucket/tata
# this does not
This does not:
%git annex unlock bucket/
%ls -li bucket/tata
33292708 -rw-rw-r-- 1 karl qbstaff 102400000 Dec 7 19:02 bucket/tata
%find . -inum 33292708
./bucket/tata
As you can see, now the inode is wrong (different from the annex object file), and the unlocked file is not a hard link.
As you can see, now the inode is wrong (different from the annex object file), and the unlocked file is not a hard link. The only difference is the argument to git annex unlock
This is really annoying, I switched to V6 for this particular feature, I have a large repository to update and it takes ages since files are copied instead of hard linked.
@ -69,6 +71,6 @@ Codename: trusty
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
Yes, we use it on a daily basis and love it.
Note that we will have to switch to LFS because gitlab no longer supports git annex from v9 release.
Note that we will have to switch to LFS for a lot of use cases because gitlab no longer supports git annex from v9 release.