Git：很难获取现有的Git存储库来跟踪新的裸远程存储库

TL; DR

您需要通过在自己的Git存储库中设置一个遥控器来启动整个过程：

git remote add <name> <URL-or-path>

after which you must use the name part you used, instead of typing out the (presumably longer) URL-or-path. That is, you'll do:

git remote add origin /d/Seafile/...
git push --set-upstream origin master

Long

Let me start by saying that I really dislike the word tracking here as it misleads everyone. It has done that to you, too.

We must use git remote to create or otherwise manipulate remotes. A remote is just a short name—like origin, which is kind of the standard first-name-to-use for a remote—that will store a URL (and some other more-internal-to-Git information).

I am retyping from your screenshot, so I may introduce typos, but the key is here in this line:

git push --set-upstream /d/Seafile/Development/gitTest/centralRepo.git master

Let's take a quick detour through the Git documentation. The syntax for git push is described in the SYNOPSIS lines of the documentation as (abbreviated):

git push [options] [repository [refspec...]]

Here, your lone option is --set-upstream (which on its own is fine) and your repository is given as a pathname, /d/Seafile/.... If you jump down to the OPTIONS section, the repository parameter is described all too briefly like this:

<repository>
The "remote" repository that is destination of a push operation. This parameter can be either a URL ... or the name of a remote ....

What is unfortunately omitted here is that --set-upstream, and the kind of tracking that you want, only works if the parameter given is a remote.

A path name like /d/Seafile/...—which your Git internally translated to D:/Seafile/... as you can see in other output—counts as a URL rather than a "remote".

Remotes and remote-tracking names

Rather than saying that a branch name tracks some other name, I like to use the phrase has as an upstream. This phrase is unfortunately a bit awkward (hence Git's use of track as a verb). Any branch name can have either no upstream at all, or one upstream. When a branch does have an upstream, that can be either:

• another branch name, e.g., develop could have master as its upstream, or
• a remote-tracking name such as origin/master.

I call names like origin/master remote-tracking names (Git documentation mostly calls these remote-tracking branch names). They come into existence by stringing together the name of a remote, such as origin, with a branch name: the name of the branch in the Git that your Git converses-with, when your Git phones up the other Git using the URL stored under that "remote".

When you use git fetch or git push, you have your Git phone up another Git. There are two Gits; each Git has its own branches. Your Git has your branches, and their Git has theirs. Your Git offers to remember their names for you, as a service ... but for your Git to remember their branch names, your Git must come up with a name for each one that does not interfere with your own branch names. Your Git does that by pasting something in front of their branch names.¹

The part that gets pasted-in-front here is the remote name, e.g., origin. Without a remote—with a URL instead—there's nothing to paste-in-front, so the pasting-in-front never happens. The --set-upstream option becomes inoperative.

So why did your Git print:

Branch 'master' set up to track remote branch 'master' from 'D:/Seafile/Development/gitTest/centrapRepo.git'.

？唯一可能的答案是，Git非常的Gitty。它只是说它做了一些物理上无法做的事情，因此没有做。

¹从技术上讲，远程跟踪名称位于单独的命名空间中：分支名称具有以开头的全拼写名称refs/heads/，所以master的确是refs/heads/master。远程跟踪名称以开头，refs/remotes/并继续包括远程名称和另一个斜杠。名称的其余部分是在该远程服务器上URL上看到的精简分支名称。因此，它们refs/heads/master成为您的信息refs/remotes/origin/master，并显示为origin/master。