blocks|key|1138462|text|在以这种方式使用git+diff时，我不知道排除路径的方法。如果有可能排除路径，那么您已经在问题中使用的神奇签名(:!)可能就是它。更多关于人类词汇魔术签名的信息。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1138463|如果有任何帮助，您可以通过添加一个作为另一个的远程来区分每个回购的提交。|1138464|cd+ProjectA
git+remote+add+ProjectB+../ProjectB
git+fetch+ProjectB
git+diff+<commit-or-branch-in-ProjectA>+<commit-or-branch-in-projectB>|code-block|syntax|javascript|1138465|当您完成扩散时，您可以移除遥控器：|1138466|git+remote+remove+ProjectB|1138467|再深入一点，当git+diff使用--no-index选项(隐式或显式)运行时，它会触发一个不同的代码路径。比较调用索引并提前返回。据我所知，索引并不称任何解析神奇路径规范的东西。|1138468|神奇的路径解析似乎是在上述代码路径返回之后发生的。具体来说，在比较中，有一个调用链树+->+oid+->+改名+->+路径规范+->+项目，这似乎就是神奇的路径解析发生的地方。|1138469|entityMap|0|LINK|mutability|MUTABLE|url|https://gitirc.eu/gitglossary.html|1|https://github.com/git/git/blob/468165c1d8a4/builtin/diff.c#L256-L470|2|https://github.com/git/git/blob/468165c1d8a4/diff-no-index.c#L236-L303|3|4|5|https://github.com/git/git/blob/468165c1d8a4/builtin/diff.c#L159-L181|6|https://github.com/git/git/blob/468165c1d8a4/tree-diff.c#L698-L715|7|https://github.com/git/git/blob/468165c1d8a4/tree-diff.c#L578-L675|8|https://github.com/git/git/blob/468165c1d8a4/pathspec.c#L529-L615|9|https://github.com/git/git/blob/468165c1d8a4/pathspec.c#L396-L491^0|8|8|1L|2|1Y|4|0|0|0|0|0|0|7|8|H|A|1I|2|1|1M|2|2|1Z|2|3|0|V|2|4|15|1|5|1A|3|6|1H|2|7|1N|4|8|1V|2|9|0^^$0|@$1|2|3|4|5|6|7|1I|8|@$9|1J|A|1K|B|C]|$9|1L|A|1M|B|C]]|D|@$9|1N|A|1O|1|1P]]|E|$]]|$1|F|3|G|5|6|7|1Q|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|1R|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|1S|8|@]|D|@]|E|$]]|$1|O|3|P|5|J|7|1T|8|@]|D|@]|E|$K|L]]|$1|Q|3|R|5|6|7|1U|8|@$9|1V|A|1W|B|C]|$9|1X|A|1Y|B|C]]|D|@$9|1Z|A|20|1|21]|$9|22|A|23|1|24]|$9|25|A|26|1|27]]|E|$]]|$1|S|3|T|5|6|7|28|8|@]|D|@$9|29|A|2A|1|2B]|$9|2C|A|2D|1|2E]|$9|2F|A|2G|1|2H]|$9|2I|A|2J|1|2K]|$9|2L|A|2M|1|2N]|$9|2O|A|2P|1|2Q]]|E|$]]|$1|U|3|-4|5|6|7|2R|8|@]|D|@]|E|$]]]|V|$W|$5|X|Y|Z|E|$10|11]]|12|$5|X|Y|Z|E|$10|13]]|14|$5|X|Y|Z|E|$10|15]]|16|$5|X|Y|Z|E|$10|15]]|17|$5|X|Y|Z|E|$10|13]]|18|$5|X|Y|Z|E|$10|19]]|1A|$5|X|Y|Z|E|$10|1B]]|1C|$5|X|Y|Z|E|$10|1D]]|1E|$5|X|Y|Z|E|$10|1F]]|1G|$5|X|Y|Z|E|$10|1H]]]]

I am not aware of a way to exclude paths when using <code>git diff</code> in this manner. If it is possible to exclude paths, the magic signature (<code>:!</code>) that you already are using in your question would perhaps be it. More info on magic signatures at <a href="https://gitirc.eu/gitglossary.html" rel="nofollow noreferrer">man gitglossary</a>.

If it is of any help, you can diff commits of each repo by adding one as a remote of the other.

<pre><code>cd ProjectA
git remote add ProjectB ../ProjectB
git fetch ProjectB
git diff &lt;commit-or-branch-in-ProjectA&gt; &lt;commit-or-branch-in-projectB&gt;
</code></pre>

When you are done diffing, you can remove the remote:

<pre><code>git remote remove ProjectB
</code></pre>

<hr>

Digging a bit deeper, it looks like when <code>git diff</code> is run with the <code>--no-index</code> option (implicitly or explicitly), it triggers a different code path. <a href="https://github.com/git/git/blob/468165c1d8a4/builtin/diff.c#L256-L470" rel="nofollow noreferrer">cmd_diff</a> calls <a href="https://github.com/git/git/blob/468165c1d8a4/diff-no-index.c#L236-L303" rel="nofollow noreferrer">diff_no_index</a> and returns early. From what I can tell, <a href="https://github.com/git/git/blob/468165c1d8a4/diff-no-index.c#L236-L303" rel="nofollow noreferrer">diff_no_index</a> does not call anything that parses magic pathspecs. 

The magic pathspec parsing seems to happen after the abovementioned code path would have already returned. Specifically, further down in <a href="https://github.com/git/git/blob/468165c1d8a4/builtin/diff.c#L256-L470" rel="nofollow noreferrer">cmd_diff</a>, there is a call chain <a href="https://github.com/git/git/blob/468165c1d8a4/builtin/diff.c#L159-L181" rel="nofollow noreferrer">builtin_diff_tree</a> -> <a href="https://github.com/git/git/blob/468165c1d8a4/tree-diff.c#L698-L715" rel="nofollow noreferrer">diff_tree_oid</a> -> <a href="https://github.com/git/git/blob/468165c1d8a4/tree-diff.c#L578-L675" rel="nofollow noreferrer">try_to_follow_renames</a> -> <a href="https://github.com/git/git/blob/468165c1d8a4/pathspec.c#L529-L615" rel="nofollow noreferrer">parse_pathspec</a> -> <a href="https://github.com/git/git/blob/468165c1d8a4/pathspec.c#L396-L491" rel="nofollow noreferrer">init_pathspec_item</a>, and this appears to be where the magic pathspec parsing happens.

blocks|key|1005644|text|我建议您只使用diff而不是git+diff来进行比较。您可以告诉diff从比较中排除某些路径，以便自定义输出。缺点是diff和git+diff的输出格式不完全相同。通常，这是不相关的，但在某些情况下，这很重要。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1005645|entityMap^0|7|4|E|8|1N|4|1S|8|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|G|$]]

I'd suggest you simply use <code>diff</code> instead of <code>git diff</code> to do the comparison. You can tell diff to exclude certain paths from the comparison in order to customize the output. Downside to this is that the output of <code>diff</code> and <code>git diff</code> is not exactly the same format. Usually, it's irrelevant, but in some cases that matters.

blocks|key|1137440|text|我在这里要说的很多是在其他答案和他们的评论中，但为了填补几个空白，强调几点，并提供我希望是一个单一的，有组织的，有用的答案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1137441|大多数形式的git+diff都希望在回购工作树中运行，以比较文件的两个版本(或一组文件中的每个版本)。对于要比较的每个文件，可能是将工作树版本与索引版本进行比较，或者将提交A中的版本与提交B中的版本进行比较。|offset|length|style|CODE|1137442|但是，在这些情况下，您无法与回购之外的东西进行比较(例如，工作树外的路径)。如果您试图引用当前回购工作树之外的内容，而git认为您正在使用这些表单之一，那么它将引发一个错误。|1137443|有一种特定形式的git+diff可以解除这一限制：|1137444|git+diff+[--no-index]+path1+path2|code-block|syntax|javascript|1137445|其中之一是：(a)包含--no-index选项，或者(b)其中一个路径位于当前回购的工作树之外。在这种情况下，git将比较文件系统上的两个任意路径。但是，与存储库相关联的git的各种特性--与历史版本相比--在使用此表单时是不可访问的。|1137446|所以，当你说|1137447|git+diff+projectA+projectB|1137448|因为你给出的路径不是都在一个回购工作树中，git认为它必须切换到这个特殊的形式，所以它是工作的。|1137449|但是：|1137450|这一种特殊的形式是相当有限的。您只需要列出两个根路径，而不是任意数量的路径规范，比如当您比较回购文件的版本时。当您开始尝试提供更通用的git+diff语法时，git会说：“好吧，这不是文件系统到文件系统的比较语法，所以我不能在工作树之外使用这个路径”.你会得到你的错误信息。|1137451|所以你有两个选择。|1137452|您可以使用git以外的工具来比较目录。这样的工具可能具有基于路径的排除功能。|1137453|或者，您可以使用git，但是可以在单个回购中进行比较。|1137454|mkdir+compare
cd+compare
git+init
git+remote+add+ProjectA+../ProjectA
git+remote+add+ProjectB+../ProjectB
git+fetch+ProjectA
git+fetch+ProjectB
git+diff+ProjectA/master+ProjectB/master|1137455|现在git明白了，您正在比较两个内容版本。|1137456|您还可以通过将ProjectB设置为ProjectA的远程(反之亦然)并进行抓取，从而使两个repos中的一个具有两个对象集。需要注意的是，仅仅删除遥控器并不一定会删除从其他回购中获取的所有对象。(它绝对不会马上把它们移除。)|1137457|entityMap^0|0|6|8|0|0|8|8|0|0|B|A|0|0|0|0|0|1V|8|0|0|0|0|0|0|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|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1L|8|@$D|1M|E|1N|F|G]]|9|@]|A|$]]|$1|L|3|M|5|N|7|1O|8|@]|9|@]|A|$O|P]]|$1|Q|3|R|5|6|7|1P|8|@$D|1Q|E|1R|F|G]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1S|8|@]|9|@]|A|$]]|$1|U|3|V|5|N|7|1T|8|@]|9|@]|A|$O|P]]|$1|W|3|X|5|6|7|1U|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1V|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|1W|8|@$D|1X|E|1Y|F|G]]|9|@]|A|$]]|$1|12|3|13|5|6|7|1Z|8|@]|9|@]|A|$]]|$1|14|3|15|5|6|7|20|8|@]|9|@]|A|$]]|$1|16|3|17|5|6|7|21|8|@]|9|@]|A|$]]|$1|18|3|19|5|N|7|22|8|@]|9|@]|A|$O|P]]|$1|1A|3|1B|5|6|7|23|8|@]|9|@]|A|$]]|$1|1C|3|1D|5|6|7|24|8|@]|9|@]|A|$]]|$1|1E|3|-4|5|6|7|25|8|@]|9|@]|A|$]]]|1F|$]]

Much of what I have to say here is in other answers and their comments, but to fill in a few blanks, emphasize a few points, and generally provide what I hope is a single, organized, useful answer:

<hr>

Most forms of <code>git diff</code> expect to be run within a repo work tree, to compare two versions of a file (or of each of a set of files). For each file to be compared, maybe you're comparing the work tree version against the index version, or the version in commit A against the version in commit B. 

In these cases, though, you can't compare against something outside your repo (e.g. a path outside the work tree). If you try to refer to something outside your current repo work tree, and git thinks you're using one of these forms, then it will raise an error. 

There is one specific form of <code>git diff</code> that lifts this restriction:

<pre><code>git diff [--no-index] path1 path2
</code></pre>

where either: (a) you include the <code>--no-index</code> option, or (b) one of the paths is outside the current repo's work tree. In that case, git will compare two arbitrary paths on your filesystem. But, various features of git that are tied to a repository - like comparing with historical versions - aren't accessible when using this form.

So, when you say

<pre><code>git diff projectA projectB
</code></pre>

since that paths you've given are not both in a single repo work tree, git figures it has to switch to this one special form, and so it works.

But:

That one special form is pretty limited. You only get to list the two root paths - not an arbitrary number of path specs, like when you compare versions of a file within a repo. When you start trying to give more general <code>git diff</code> syntax, then git says "well, this isn't the filesystem-to-filesystem comparison syntax, so I can't have this path outside the work tree"... and you get your error message.

So you have two choices.

You can use a tool other than git to compare the directories. Such a tool might have functionality for path-based exclusions.

Or, you can use git, but do the comparison within a single repo.

<pre><code>mkdir compare
cd compare
git init
git remote add ProjectA ../ProjectA
git remote add ProjectB ../ProjectB
git fetch ProjectA
git fetch ProjectB
git diff ProjectA/master ProjectB/master
</code></pre>

Now git understands that you're comparing two content versions.

You can also do this by just making ProjectB a remote of ProjectA (or vice versa) and fetching so that one of the two repos has both sets of objects. The thing to watch for is, just deleting the remote doesn't necessarily remove all of the objects fetched from the other repo. (It definitely doesn't remove them right away.)

I am trying to do a git diff between two separate repositories. Using <code>git diff ProjectA ProjectB</code> alone works, but I have to scroll through all the differences in the <code>.git</code> directory.

I've tried <code>git diff ProjectA ProjectB -- . ':!.git'</code> to exclude the <code>.git</code> directory, but I get the following error.

<pre><code>Not a git repository
To compare two paths outside a working tree:
usage: git diff [--no-index] &lt;path&gt; &lt;path&gt;
</code></pre>

I've also tried <code>git diff --no-index ProjectA ProjectB -- . ':!.git'</code> but simply receive the message:

<pre><code>usage: git diff --no-index &lt;path&gt; &lt;path&gt;
</code></pre>

What is the correct way to git diff two different repositories while excluding certain directories?

Exclude directories from git diff on two separate repositories

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我试图在两个独立的存储库之间做一个git。单独使用git diff ProjectA ProjectB是可行的，但我必须浏览.git目录中的所有差异。我尝试过git diff ProjectA ProjectB -- . ':!.git'来排除.git目录，但是我得到了以下错误。Not a git repository...

问将目录排除在两个独立存储库的git diff中
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问将目录排除在两个独立存储库的git diff中EN