Markus Teich <markus.te...@stusta.mhn.de> writes: > git will break them. It calls unlink and create on every update. > > At the moment I am thinking about the GIT_DIR in $HOME/somthing/deeper > and setting the GIT_WORK_TREE to $HOME after cloning, making backups > of possibly already existing files and moving the cloned files to > $HOME. > Handling templated configfiles (you don't want your ssh hosts in the > repo) seems to be a bit problematic though. > Any other objections to this method?
I do it like that: alias homegit="GIT_DIR=~/prj/dotfiles/.git GIT_WORK_TREE=~ git" And then call "homegit commit" etc. -- Christian Neukirchen <chneukirc...@gmail.com> http://chneukirchen.org