Re: git-annex - documentation clarification - I've had data loss
(here it is again -- to the list!) Thanks Joey. I still think it should be mentioned up front that the the 'add' actually moves the file. It's a clear difference to how git works. Interesting about direct mode; I hadn't heard of it and was about to request such a feature! Thanks Sean and Klaus too. I thought as a newb I'd hold off editing the wiki for now. Good point on the forensics. Although you can tell I'm not too upset; most of the data if not all was downloaded from net and could be downloaded again. Regards, Matt On Tue, Feb 11, 2014 at 3:02 AM, Joey Hess wrote: > Matthew Hannigan wrote: >> Anyway, time passes, and I decide to move all this content over to a >> different disk. >> I just used drag and drop from a gui (not sure whether windows or >> linux) and of course the select doesn't pick up the .git directory. >> >> Next I reformated the disk, and get a funny feeling that the copy went >> a little too fast ... >> >> >> Can I suggest that the following wording be changed from this: >> "When you add a file to the annex and commit it, only a symlink to the >> annexed content is committed. The content itself is stored in >> git-annex's backend." >> >> to this: >> When you add a file to the annex, the content is moved to git-annex's >> backend (.git/annex/..) and replaced with a symlink. The commit only >> commits the symlink. > > I've made a similar wording change. > > Thanks for taking an unfortunate mistake and turning it constructive! > >> The http://git-annex.branchable.com/how_it_works/ page might be >> improved the same way. >> It currently says >> "The contents of large files are not stored in git, only the names of >> the files and some other metadata remain there." >> which is strictly true but might lead others to make the same mistaken >> assumption that I did. > > I think the next paragraph after that explains it well enough there. > > -- > see shy jo -- m a t t h e w l i n u s h a n n i g a n ___ vcs-home mailing list vcs-home@lists.madduck.net http://lists.madduck.net/listinfo/vcs-home
Re: git-annex - documentation clarification - I've had data loss
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Just a hint to eventually get your data back: Am Mo den 10. Feb 2014 um 13:50 schrieb Matthew Hannigan: > Next I reformated the disk, and get a funny feeling that the copy went > a little too fast ... Try to use some forensic tools. If you just formated your disk and did not write any data to it, the change is high that you get back most of the files in case of mp3/video/images. Regards Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQGcBAEBCgAGBQJS+QJ0AAoJEKZ8CrGAGfasMQQL/RlnCSXinqIrJjSV1rI7Q4zi NGQk/w7qT+jJ8XXYyMDnoAv+himrvk+cMvVXjE/8CvwGutDKwvXvX2zxUaC8yBjo /H4hZAxQwVENDRtfiGo5+HxrYgUUbv0vpqK0r05ddXK5JZ7YYMuLFP8y2TAVzcQl VYyX3NkACmpLkTPYTSt4C1QYQjcuJV/vQ+LydXYA0nW+kuBHgo4q+F3EMw5K5HPi mlkfIzGZWh/+z5EFJcfxvLDiF4xSgO6B2cX7SUFMt/B5Qwp1TotTdG/dtR3KXo7B EM3P3qsyONDyjELXkBgOZIWgbbcZqXSJZOqY+BtoTmQc9F5pkI4DOLIqmqKLpIRC 4SnHtsDelAOH4Aribu8Puq6QSOgNgugOiTN+v3MxhvPMI4XSFZNCxu4n3z68Dwmp 1vkNHGWc3kaxVHhFvyOstySTElNx7Q/Q8Ap0Yg24Td6LfcgZ2OsJ2kHEdmUvSCz9 ZrtbSrjZAbnZCnC8YYTRKWSTkhQE1xnyAX5hS4FLTA== =2Mdb -END PGP SIGNATURE- ___ vcs-home mailing list vcs-home@lists.madduck.net http://lists.madduck.net/listinfo/vcs-home
Re: git-annex - documentation clarification - I've had data loss
Matthew Hannigan wrote: > Anyway, time passes, and I decide to move all this content over to a > different disk. > I just used drag and drop from a gui (not sure whether windows or > linux) and of course the select doesn't pick up the .git directory. > > Next I reformated the disk, and get a funny feeling that the copy went > a little too fast ... > > > Can I suggest that the following wording be changed from this: > "When you add a file to the annex and commit it, only a symlink to the > annexed content is committed. The content itself is stored in > git-annex's backend." > > to this: > When you add a file to the annex, the content is moved to git-annex's > backend (.git/annex/..) and replaced with a symlink. The commit only > commits the symlink. I've made a similar wording change. Thanks for taking an unfortunate mistake and turning it constructive! > The http://git-annex.branchable.com/how_it_works/ page might be > improved the same way. > It currently says > "The contents of large files are not stored in git, only the names of > the files and some other metadata remain there." > which is strictly true but might lead others to make the same mistaken > assumption that I did. I think the next paragraph after that explains it well enough there. -- see shy jo signature.asc Description: Digital signature ___ vcs-home mailing list vcs-home@lists.madduck.net http://lists.madduck.net/listinfo/vcs-home
