Another way, which wouldn't require environment variables or extra parameters for each command is moving the .git directory, and replace it with a file called .git, which has the path to the actual .git directory. Git submodules use this feature too. On Sun, Apr 20, 2014 at 11:49 AM, Duy Nguyen <pclouds@xxxxxxxxx> wrote: > On Sun, Apr 20, 2014 at 4:13 PM, Miller, Hugh <HughMiller@xxxxxxxxxxx> wrote: >> Dear Community, >> >> Is there any way to use .git (e.g., a different set of "client" commands) that allows the .git folder to be placed in a location away from the actual files being versioned ? For example, can one set environment variables that let the software know where the .git folder is ? > > Try > > git --git-dir=<new .git location> --work-tree=<top work tree location> > <some command> > > The reason of two arguments instead of one is because .git is also > used to mark top work tree location, which is now lost after you move > .git elsewhere. You could also set environment variables GIT_DIR and > GIT_WORK_TREE, which have the same effect. "man git" for details. > -- > Duy > -- > 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 -- 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