Hi Seth, On Tue, Jan 10, 2012 at 04:24:50PM -0500, Seth Robertson wrote: > > In message <20120110211548.GD10255@xxxxxxxxxxxxxxxxxxxx>, Jason writes: > > The nuts and bolts of this aren't difficult, the problem is I don't have > a complete understanding of how git stores data. I've heard in the > past that it uses a lot of hardlinks and softlinks. I need to make > sure, that once I transfer the data, and reboot the machine with the new > partition mounted under /home, that all my git repos will be okay. > > Under most circumstances, git will do the right thing. Only if you > use specific flags on clone (like --shared or --reference) might > something go wrong, and as the manual page explains, you can use > git-repack to undo these. > > The real solution is, after you rsync, to: > > for f in */.git; do (cd $f; git fsck >&/dev/null || echo "$f is BAD!!"); done Okay, I've been using the new system for a week or so now, and everything looks good. Thanks! Before the transfer, I went ahead and did the above to make sure the repos were good to begin with. All 279 of them were fine, both before and after. thx, Jason. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html