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:
http://a-or-b.myopenid.com/ 2012-01-03 00:43:54 +00:00 committed by admin
parent ddc4b3de33
commit 9f7ca3fe0d
1 changed files with 19 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
doc/forum/Handling_web_special_remote_when_content_changes__63__.mdwn Normal file
View file

@ -0,0 +1,19 @@
I am in the process of organising all of my documents (pdf/ps/etc.) and putting them into an annex. It seems like the easiest (and smartest?) way for me to manage my 15,000+ document library... (Yeah, I've not read them all!)
However, one of the issues I have run into is when I want to include something like a software manual...
I'm not even sure if git-annex is the correct way to handle these sort of document, but...
What would you do if the URL stays the same, but the file content changes over time?
For example, the administration manual for R gets updated and re-released for each release of R, but the URL stays the same.
http://cran.r-project.org/doc/manuals/R-admin.pdf
I'm not particularly worried about whether my annex version is the most recent, just that if I want to 'annex get' it, it will pull *a* version from somewhere.
Any thoughts?
I'd bet that the SHA-hash would change between releases(!) so would a WORM backend be the best approach? It would mess up my one-file-in-multiple-directories (i.e. multiple simlinks to the one SHA-...-.....) approach.