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

Added a comment: It works!

Browse source
This commit is contained in:
http://www.openid.albertlash.com/openid/ 2012-10-24 22:00:31 +00:00 • committed by admin
parent 1d3a9dd2d5
commit a74b896982
1 changed files with 13 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

13
doc/forum/Managing_a_large_number_of_files_archived_on_many_pieces_of_read-only_medium___40__E.G._DVDs__41__/comment_6_55a4a3616ea59654da1c2f9902561e3b._comment Normal file
View file

@ -0,0 +1,13 @@
[[!comment format=mdwn
username="http://www.openid.albertlash.com/openid/"
ip="74.96.185.87"
subject="It works!"
date="2012-10-24T22:00:31Z"
content="""
This works great! I first tried it with WORM, no-go. I can see why the SHA backends are so powerful, they appear to circumvent the commits which git usually uses for merging. When I first do the merge, it reports this:
warning: no common commits
Compared to how I've managed CD/DVD backups in the past, this is a quantum leap forward, and I don't find it convoluted in comparison. Yes, there is dar, but I prefer this method. In my case, its the perfect solution for original files, which in generally are treated as immutable, and not accessed very often. They are usually large, too! I'm using them for digital pictures.
"""]]