On Mon, Oct 13, 2008 at 10:51 PM, Brandon <siamesedream01@xxxxxxxxx> wrote: > You can use "git config core.worktree <location>" to create a ".git" > folder that manages a working copy in another location. > > I know some of the GUI tools don't support this though so I would only > use it if truly necessary . (For example a using git to manage a > mapped network drive, it would be faster to keep the ".git" folder on > the local harddrive) > > More documentation here: http://www.kernel.org/pub/software/scm/git/docs/ > > On Mon, Oct 13, 2008 at 2:40 PM, David Tweed <david.tweed@xxxxxxxxx> wrote: >> On Mon, Oct 13, 2008 at 7:19 PM, Shawn O. Pearce <spearce@xxxxxxxxxxx> wrote: >>> # then every once in a while, or from a cron job >>> $ git push --all backup >>> >>> Of course since Git is distributed you can you use this same approach >>> to make backups to other systems. You can even edit the .git/config >>> to give the [remote "backup"] section more than one url line, so >>> that "git push --all backup" will send updated copies to multiple >>> locations at once. >> >> Another advantage of 'git push'ing to another repository (possibly via >> cron) as backup is that (for technical reasons) git push has to >> 'parse' the new changes to your repository in order to push, so it is >> likely to spot corruption (eg, dying disk) at that time and when you >> can decide what to do about it. (I have enough backups all over the >> place that I don't worry about not having a 'copy' of any stuff I care >> about, but that there'll be some fatal corruption I don't notice >> immediately that then gets propagated everywhere rendering them >> useless.) >> >> -- >> cheers, dave tweed__________________________ >> david.tweed@xxxxxxxxx I have the same problem as David, but I manage it by using a symlink. That is my .git folder is a symlink to the real repository (possibly on another partition). (So far I had no problems with this setup.) Ciprian Dorin Craciun. -- 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
