blocks|key|1635802|text|假设你的myfiles目录已经存在，并且有一些内容，你能接受这个吗？|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1635803|cd+~/backup
git+init
git+add+myfiles|code-block|syntax|javascript|1635804|.git目录将位于backup中，而不是myfiles中。|1635805|entityMap^0|4|7|0|0|0|4|9|6|K|7|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|N|$]]

Assuming your <code>myfiles</code> directories already exists and has some content, could you live with this:

<pre><code>cd ~/backup
git init
git add myfiles
</code></pre>

The <code>.git</code> directory will be in <code>backup</code>, not in <code>myfiles</code>.

blocks|key|1420978|text|git+--git-dir=../repo+--work-tree=.+add+foo|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|1420979|这会做你想做的事情，但是当你不得不在你使用的每个git命令中指定它时，这显然会很糟糕。|unstyled|1420980|你可以导出GIT_WORK_TREE=.和GIT_DIR=../backup，Git会在每个命令中提取它们。不过，这只能让您轻松地在每个shell的单个存储库中工作。|offset|length|style|CODE|1420981|我更倾向于将.git目录符号链接到其他地方，或者从您的主备份目录创建一个指向.git目录的符号链接。|1420982|entityMap^0|0|0|5|F|L|H|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|R|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|S|8|@$I|T|J|U|K|L]|$I|V|J|W|K|L]]|9|@]|A|$]]|$1|M|3|N|5|F|7|X|8|@]|9|@]|A|$]]|$1|O|3|-4|5|F|7|Y|8|@]|9|@]|A|$]]]|P|$]]

<pre><code>git --git-dir=../repo --work-tree=. add foo
</code></pre>

This will do what you want but will obviously suck when you have to specify it with every git command you ever use.

You can export <code>GIT_WORK_TREE=.</code> and <code>GIT_DIR=../backup</code> and Git will pick them up on each command. That will only comfortably allow you to work in a single repository per shell, though.

I’d rather suggest symlinking the .git directory to somewhere else, or creating a symlink to the .git directory from your main backup directory.

blocks|key|1421040|text|通常将一个目录命名为git存储库，它的工作树位于一个不寻常的位置，带有一个'.git‘扩展名，就像一个空存储库。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1421041|mkdir+../git_repos/myfiles.git|code-block|syntax|javascript|1421042|如果您在初始化时提供了--work-tree选项，那么这将自动设置core.worktree配置变量，这意味着一旦您指定了git目录，git就会知道在哪里可以找到工作树。|offset|length|style|CODE|1421043|git+--git-dir=../git_repos/myfiles.git+--work-tree=.+init|1421044|但您也可以在事后设置此变量。|1421045|git+--git-dir=../git_repos/myfiles.git+config+core.worktree+"$(pwd)"|1421046|完成此操作后，add命令应按预期工作。|1421047|git+--git-dir=../git_repos/myfiles.git+add+foo|1421048|entityMap^0|0|0|B|B|X|D|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|10|8|@$I|11|J|12|K|L]|$I|13|J|14|K|L]]|9|@]|A|$]]|$1|M|3|N|5|D|7|15|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|16|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|17|8|@]|9|@]|A|$E|F]]|$1|S|3|T|5|6|7|18|8|@]|9|@]|A|$]]|$1|U|3|V|5|D|7|19|8|@]|9|@]|A|$E|F]]|$1|W|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|X|$]]

It's conventional to name a directory that is a git repository that has its working tree in an unusual place with a '.git' extension, much like a bare repository.

<pre><code>mkdir ../git_repos/myfiles.git
</code></pre>

If you had provided the <code>--work-tree</code> option at init time then this would have automatically set up the <code>core.worktree</code> config variable that means that git will know where to find the working tree once you specify the git directory.

<pre><code>git --git-dir=../git_repos/myfiles.git --work-tree=. init
</code></pre>

But you can set this variable after the fact as well.

<pre><code>git --git-dir=../git_repos/myfiles.git config core.worktree "$(pwd)"
</code></pre>

Once you've done this, the add command should work as expected.

<pre><code>git --git-dir=../git_repos/myfiles.git add foo
</code></pre>

blocks|key|1421153|text|你可以创建一个"nodgit“脚本(No+Dot+GIT)，像这样|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1421154|#!/bin/sh
gits=/usr/local/gits
++++x=`pwd`
++++testdir()+{(+cd+$1;+pwd;+)}
++++while+[+"$x"+!=+"/"+];+do
++++++y=`echo+$x%7Csed+-e+"s/\//__/g"`
++++++if+([+-d+"$gits/$y"+]);+then
++++++++export+GIT_DIR="$gits/$y"
++++++++export+GIT_WORK_TREE="$x"
++++++++if+([+"$1"+=+"nodinit"+]);+then
++++++++++mkdir+-p+"$GIT_DIR"
++++++++++git+init+--bare;+exit+$?
++++++++elif+([+"$1"+=+"shell"+]);+then
++++++++++bash;+exit+$?
++++++++else
++++++++++exec+git+"$@"
++++++++fi
++++++fi
++++++x=`testdir+"$x/.."`
++++done|code-block|syntax|javascript|1421155|您可以调用nodgit来代替git，它会根据需要通过查找git代码库来设置变量。例如，假设您在/usr/local/gits/__home__foo_wibble中有一个(裸)+repo，并且您在/home/foo/wibbles/one中，那么它将找到正确的工作目录(/home/foo/wibble)和repo。|1421156|哦，你也可以使用"nodgit+git+shell“来获得一个设置了正确变量的shell，这样你就可以使用普通的git命令了。|1421157|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

You could create a "nodgit" script (No Dot GIT) with somet like

<pre><code>#!/bin/sh
gits=/usr/local/gits
 x=`pwd`
 testdir() {( cd $1; pwd; )}
 while [ "$x" != "/" ]; do
 y=`echo $x|sed -e "s/\//__/g"`
 if ([ -d "$gits/$y" ]); then
 export GIT_DIR="$gits/$y"
 export GIT_WORK_TREE="$x"
 if ([ "$1" = "nodinit" ]); then
 mkdir -p "$GIT_DIR"
 git init --bare; exit $?
 elif ([ "$1" = "shell" ]); then
 bash; exit $?
 else
 exec git "$@"
 fi
 fi
 x=`testdir "$x/.."`
 done
</code></pre>

You can call nodgit in place of git and it will set variables as necessary by looking for a git repo. For example say you have a (bare) repo in /usr/local/gits/__home__foo_wibbles and you are in in /home/foo/wibbles/one then it will find the correct working directory (/home/foo/wibbles) and repo.

Oh you can also use "nodgit shell" to get a shell with the correct vars set so you can use plain old git commands.

blocks|key|1636078|text|在存储库中使用git：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1636079|cd+./backup/git_repos/myfiles
git+init+--bare
git+config+core.worktree+../myfiles
git+config+core.bare+false|code-block|syntax|javascript|1636080|从现在开始，您可以在./backup/git_repos/myfiles目录中使用git，而无需设置任何环境变量或其他参数。|1636081|entityMap^0|7|3|0|0|A|Q|15|3|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|X|8|@]|D|@]|E|$]]]|N|$]]

Use <code>git</code> inside the repo:

<pre><code>cd ./backup/git_repos/myfiles
git init --bare
git config core.worktree ../myfiles
git config core.bare false
</code></pre>

From now on, you can use <code>git</code> inside the <code>./backup/git_repos/myfiles</code> directory, without setting any environment variables or additional parameters.

blocks|key|1636143|text|在我的git版本(1.7.11.3)上，可以使用git+init+(和git+clone)的--separate-git-dir选项来实现这一点。该选项将git存储库从工作树中分离出来，并在工作树的根目录中创建一个文件系统不可知的git符号链接(以名为.git的文件的形式)。我认为结果和niks'+answer是一样的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1636144|git+init+--separate-git-dir+path/to/repo.git+path/to/worktree|code-block|syntax|javascript|1636145|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/8603156/600840^0|9|8|O|8|Z|9|1A|I|3I|4|40|C|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]|$9|11|A|12|B|C]]|D|@$9|13|A|14|1|15]]|E|$]]|$1|F|3|G|5|H|7|16|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|17|8|@]|D|@]|E|$]]]|L|$M|$5|N|O|P|E|$Q|R]]]]

The <code>--separate-git-dir</code> option for <code>git init</code> (and <code>git clone</code>) can be used to accomplish this on my version of git (<code>1.7.11.3</code>). The option separates the git repository from the work tree and creates a filesystem agnostic git symbolic link (in the form of a file named <code>.git</code>) in the root of the work tree. I think the result is identical to <a href="https://stackoverflow.com/a/8603156/600840">niks' answer</a>.

<pre><code>git init --separate-git-dir path/to/repo.git path/to/worktree
</code></pre>

blocks|key|1636219|text|我创建的脚本看起来像|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1636220|~/bin/git-slash：|1636221|#!/usr/bin/sh

export+GIT_DIR=/home/Version-Control/cygwin-root.git/
export+GIT_WORK_TREE=/

git+--git-dir=$GIT_DIR+--work-tree=$GIT_WORK_TREE+"$@"

exit+$?|code-block|syntax|javascript|1636222|使用--git_dir=$GIT_DIR是多余的，但是提醒我也可以在脚本之外设置环境变量。|1636223|上面的示例用于跟踪cygwin系统文件的本地更改。|1636224|我可以为任何需要它的大型项目制作一个这样的脚本--但是/没有/.git是我的主要用途。|1636225|如果您消除了冗余，上面的代码就足够小，可以创建一个shell别名或函数。|1636226|如果我这样做的次数足够多，我会恢复工作区到存储库的映射|1636227|"Boxes,+Links,+and+Parallel+Trees:+Elements+of+a+Configuration+Management+System",+
in+Workshop+Proceedings+of+the+Software+Management+Conference.+1989.|1636228|其最接近的现代对应物是Perforce+mappings+or+views，支持部分签出以及工作区和存储库的非托管。|offset|length|1636229|entityMap|0|LINK|mutability|MUTABLE|url|https://www.perforce.com/perforce/doc.091/manuals/cmdref/o.views.html%2520%2522Perforce%2520workspace/branch%2520mappings%2520or%2520views^0|0|0|0|0|0|0|0|0|0|B|Q|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|17|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|18|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|19|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|1A|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1B|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1C|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1D|8|@]|9|@]|A|$]]|$1|S|3|T|5|F|7|1E|8|@]|9|@]|A|$G|H]]|$1|U|3|V|5|6|7|1F|8|@]|9|@$W|1G|X|1H|1|1I]]|A|$]]|$1|Y|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]]|Z|$10|$5|11|12|13|A|$14|15]]]]

I create scripts that look like

~/bin/git-slash:

<pre><code>#!/usr/bin/sh

export GIT_DIR=/home/Version-Control/cygwin-root.git/
export GIT_WORK_TREE=/

git --git-dir=$GIT_DIR --work-tree=$GIT_WORK_TREE "$@"

exit $?
</code></pre>

It's redundant to use --git_dir=$GIT_DIR, but reminds me that I can also set environment variables outside the script.

The above example is for tracking local changes to cygwin system files.

Can make one such script for any major project that needs this - but / without /.git is my main use.

The above is small enough to make a shell alias or function, if you eliminate the redundancy.

If I do this often enough, I would revive the workspace to repository mapping of 

<pre><code>"Boxes, Links, and Parallel Trees: Elements of a Configuration Management System", 
in Workshop Proceedings of the Software Management Conference. 1989.
</code></pre>

whose closest modern counterpart is <a href="https://www.perforce.com/perforce/doc.091/manuals/cmdref/o.views.html%20%22Perforce%20workspace/branch%20mappings%20or%20views" rel="nofollow noreferrer">Perforce mappings or views</a>, supporting partial checkouts as well as non-colocation of workspace and repo.

blocks|key|1636327|text|选项1:+core.worktree|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1636328|在您想要跟踪的路径之外初始化一个非裸存储库，并将core.worktree设置为您想要跟踪的路径。您可以使用终端命令来设置此值，或者直接编辑存储库配置文件来添加：|offset|length|style|CODE|1636329|worktree+=+<path+to+files+to+backup>|1636330|不要将存储库文件夹设置为此路径的子文件夹，这将是递归的。您可以尝试这样做，然后直接忽略存储库文件夹，但我认为git不会允许这种情况。|1636331|在您的示例中，您可以转到backup/git_repos/+to+run+the+init+dir--git-command+and+could+use+the=./myfiles`选项来覆盖默认的存储库文件夹名称。这些命令将如下所示：|1636332|cd+backup/git_repos+
git+init+--git-dir=./myfiles
git+config+core.worktree+backup/myfiles|code-block|syntax|javascript|1636333|注意:我最近测试了很多windows版的git，只有Git扩展支持使用core.worktree来移动主工作树。|1636334|不支持core.worktree的GUI|1636335|SourceTree、福克、塔式、GitKraken、GitHub台式机、GitAhead、SmartGit*和可口可乐。在使用core.worktree时，您需要坚持使用终端。|1636336|*+SmartGit将此功能与选项2合并，并要求提供.git文件。对于core.worktree，这不是必需的。|1636337|选项2：--separate-git-dir|1636338|使用初始化位置中包含以下行的--separate-git-dir=<path+to+hold+repository+data>.+This+will+use+the+specified+path+to+hold+the+repository+data+and+create+a+.git`文件，在要备份的路径上初始化存储库：|1636339|gitdir:+<path+to+hold+repository+data>|1636340|对于您来说，这些命令将如下所示：|1636341|cd+backup/myfiles
git+init+--separate-git-dir=backup/git_repos/myfiles/|1636342|backup/myfiles/中的.git文件将包含gitdir:+backup/git_repos/myfiles/|1636343|现在，您可以操作git，将.git文件的位置视为存储库位置。|1636344|entityMap^0|0|O|D|0|0|10|0|0|C|S|1J|P|0|0|0|0|0|Q|4|0|0|E|3G|0|0|12|0|0|0|0|F|H|4|Q|X|0|D|4|0^^$0|@$1|2|3|4|5|6|7|1G|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1H|8|@$D|1I|E|1J|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|1K|8|@$D|1L|E|1M|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|1N|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1O|8|@$D|1P|E|1Q|F|G]|$D|1R|E|1S|F|G]]|9|@]|A|$]]|$1|N|3|O|5|P|7|1T|8|@]|9|@]|A|$Q|R]]|$1|S|3|T|5|6|7|1U|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1V|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1W|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1X|8|@$D|1Y|E|1Z|F|G]]|9|@]|A|$]]|$1|10|3|11|5|6|7|20|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|21|8|@$D|22|E|23|F|G]]|9|@]|A|$]]|$1|14|3|15|5|6|7|24|8|@$D|25|E|26|F|G]]|9|@]|A|$]]|$1|16|3|17|5|6|7|27|8|@]|9|@]|A|$]]|$1|18|3|19|5|P|7|28|8|@]|9|@]|A|$Q|R]]|$1|1A|3|1B|5|6|7|29|8|@$D|2A|E|2B|F|G]|$D|2C|E|2D|F|G]|$D|2E|E|2F|F|G]]|9|@]|A|$]]|$1|1C|3|1D|5|6|7|2G|8|@$D|2H|E|2I|F|G]]|9|@]|A|$]]|$1|1E|3|-4|5|6|7|2J|8|@]|9|@]|A|$]]]|1F|$]]

<h2>Option 1: core.worktree</h2>
Initialize a non-bare repository outside of the path you want to track and set <code>core.worktree</code> to the path you want to track. You can do this using terminal commands to set this value or directly edit the repository config file to add:
<code>worktree = &lt;path to files to backup&gt;</code>
Do not make the repository folder a subfolder of this path, that would be recursive. You could possibly try this and simply ignore the repository folder, but I think git won't allow this scenario.
In your case, you would go to <code>backup/git_repos/ to run the </code>init<code>command and could use the</code>--git-dir=./myfiles` option to override the default repository folder name. The commands would look like this:
<pre><code>cd backup/git_repos 
git init --git-dir=./myfiles
git config core.worktree backup/myfiles
</code></pre>
NOTE: I recently tested a great many git GUIs for windows and only Git Extensions supports using core.worktree to move the main working tree.
GUIs that do not support core.worktree
SourceTree, Fork, Tower, GitKraken, GitHub Desktop, GitAhead, SmartGit*, and Git-Cola. You will want to stick to the terminal when using core.worktree.
* SmartGit conflaits this feature with Option 2 and is asking for a <code>.git</code> file. This is not required for core.worktree.
<h2>Option 2: --separate-git-dir</h2>
Initialize a repository at the path you want to backup using <code>--separate-git-dir=&lt;path to hold repository data&gt;. This will use the specified path to hold the repository data and create a </code>.git` file in the initialization location that contains a line like this:
<code>gitdir: &lt;path to hold repository data&gt;</code>
For you, the commands would look like this:
<pre><code>cd backup/myfiles
git init --separate-git-dir=backup/git_repos/myfiles/
</code></pre>
And your <code>.git</code> file in <code>backup/myfiles/</code> will contain <code>gitdir: backup/git_repos/myfiles/</code>
You now operate git treating the location of the <code>.git</code> file as it that was the repository location.

I have an unusual idea to use git as a backup system. So let's say I have a directory ./backup/myfiles and I want to back that up using git. To keep things clean I don't want to have a .git directory in the myfiles folder, so I thought I could create ./backup/git_repos/myfiles. From looking at the git docs, I've tried doing this:

<pre><code>$ cd backup/myfiles
$ mkdir ../git_repos/myfiles
$ git --git-dir=../git_repos/myfiles init
Initialized empty Git repository in backup/git_repos/myfiles/
$ git --git-dir="../git_repos/myfiles/" add foo
fatal: pathspec 'foo' did not match any files
</code></pre>

You can see the error message I get there. What am I doing wrong?

Can I store the .git folder outside the files I want tracked?

文件系统

GitHub

我有一个不同寻常的想法，使用git作为备份系统。假设我有一个目录./backup/myfiles，我想使用git备份它。为了保持干净，我不想在myfiles文件夹中有一个备份目录，所以我想我可以创建./ .git /git/myfiles。通过查看git文档，我尝试这样做：$ cd backup/myfiles$ mk...

问是否可以将.git文件夹存储在要跟踪的文件之外？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问是否可以将.git文件夹存储在要跟踪的文件之外？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问是否可以将.git文件夹存储在要跟踪的文件之外？
EN