On Sun, Feb 24, 2008 at 3:08 PM, Remi Vanicat <vanicat@xxxxxxxxxx> wrote: > "Alexander Gladysh" <agladysh@xxxxxxxxx> writes: > > > I thought to construct my repo of the number of symlinks to other > > places, but apparently Git does not follow any simlinks. > > I use "reverse" symlinks: the files i want to manage are replaced by > symlink to the file that is in then git repository: > > my home contain: > > .abbrev_defs -> .myconfig/abbrev_defs > .bash_logout -> .myconfig/bash_logout [...] > > and a .myconfig git repository that manage those file. For configuration files I tend to actually physically copy them to a directory under the tree that I'm archiving using git, just because it feels slightly safer. If something git related goes wrong (probably due to my input) it can't, eg, stick an old, corrupted version of, eg, .bashrc in my home directory, which stops terminal login when I next reboot. (I had something similar happen when I actually had the live version of my archiving script being put into the archive. When I checked out a previous tree to look at something, an old buggy archiving script got checked out and created half a dozen corrupt commits I had to reset away.) Of course, the odds of anything like this happening in practice are quite small. -- cheers, dave tweed__________________________ david.tweed@xxxxxxxxx Rm 124, School of Systems Engineering, University of Reading. "while having code so boring anyone can maintain it, use Python." -- attempted insult seen on slashdot - 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
