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

comment and reject

Browse source
This commit is contained in:
Joey Hess 2021-01-29 14:33:26 -04:00
parent f8a13fbbce
commit fbf53c320d
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 17 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
doc/bugs/special_directory_remotes__58___git_annex_copy_fails_if_tmp__47___is_a_symbolic_link_to_another_device.mdwn
View file

@ -21,3 +21,4 @@ MacOS High Sierra 10.13.6
### 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)
Of course! git-annex is totally amazing in order to manage big collections of files. I'm using it for my videos, and for my photos as well (thousands of files), on Linux and MacOS. Thank you very much for this awesome tool!
> [[closing|done]] per my comment --[[Joey]]

16
doc/bugs/special_directory_remotes__58___git_annex_copy_fails_if_tmp__47___is_a_symbolic_link_to_another_device/comment_2_993f86881ae46fbd1c402626c6380ece._comment Normal file
View file

@ -0,0 +1,16 @@
[[!comment format=mdwn
username="joey"
subject="""comment 2"""
date="2021-01-29T18:28:30Z"
content="""
The directory special remote writes to a directory under the "tmp"
directory, and then it renames that into place. Amoung other things that
makes the update happen atomically. If "tmp" is on another filesystem than
the final destination, a rename won't work.
I just don't see any point in making this be supported, because if it were,
git-annex would have to first write to the "tmp" directory, and then
re-write the same files all over again to the final destination. So making
the tmp directory be on a faster device can't actually speed anything up.
It would just make it slower.
"""]]