summaryrefslogtreecommitdiff
path: root/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
blob: ab971dab5e40722752df2144b9e33e240de0cc16 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
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.

"""]]