Question

我清楚地理解,Gite如何能够支持档案移动:由于它使用档案库,很容易发现“附加”文件与“移走”一样。

我的问题是,是否令人振奋:考虑到 Java,一揽子声明的改动,因此档案内容与NOT相同。在这种情况下,Gite如何确定“附加”的档案与“移走”的档案共享历史? 如果我只做了微小改动或类似的非决定性解决办法,它是否检查了“最相似的内容”?

Answer 1

如Git FAQ所述,它将根据回忆情况发现类似内容。

吉唐不得不与许多不同的工作流程进行互动,例如,一些变化可能来自派系,那里可能无法提供更名人的信息。依靠明确改称的跟踪,不可能将两 trees树混为一谈,只有两.(create/delete)是一片(create/delete)的树木,而另一.是使用某种其他冷却。

在第二份说明中,重新命名的跟踪实际上只是追踪树木内容移动情况的一个特殊案例。在某些情况下,你可能有兴趣询问何时添加职能或转移到另一个档案。只有在需要时,才依靠重新整理这一信息的能力,因此,Gite的目的是提供更灵活的方式,追踪你的树木是如何变化的。

However, this does not mean that Git has no support for renames.
The diff machinery in Git has support for automatically detecting renames, this is turned on by the -M switch to the git-diff-* family of commands.
The rename detection machinery is used by git-log(1) and git-whatchanged(1), so for example, git log -M will give the commit history with rename information.
Git also supports a limited form of merging across renames.
The two tools for assigning blame, git-blame(1) and git-annotate(1) both use the automatic rename detection code to track renames.

<http://git-scm.com/docs/git-log” rel=“nofollow noreferer”>gitlog<<>>a>向您提供了一些有关这种回忆的详细信息:

-B[<n>][/<m>]

完全改写为删除和制造的鞋子。这有两个目的:

It affects the way a change that amounts to a total rewrite of a file not as a series of deletion and insertion mixed together with a very few lines that happen to match textually as the context, but as a single deletion of everything old followed by a single insertion of everything new, and the number m controls this aspect of the -B option (defaults to 60%).
-B/70% specifies that less than 30% of the original should remain in the result for git to consider it a total rewrite (i.e. otherwise the resulting patch will be a series of deletion and insertion mixed together with context lines).

When used with -M, a totally-rewritten file is also considered as the source of a rename (usually -M only considers a file that disappeared as the source of a rename), and the number n controls this aspect of the -B option (defaults to 50%).
-B20% specifies that a change with addition and deletion compared to 20% or more of the file s size are eligible for being picked up as a possible source of a rename to another file.

-M[<n>]

If generating diffs, detect and report renames for each commit. For following files across renames while traversing history, see --follow.
If n is specified, it is a is a threshold on the similarity index (i.e. amount of addition/deletions compared to the file s size).
For example, -M90% means git should consider a delete/add pair to be a rename if more than 90% of the file hasn t changed.

其他参考资料:

Linus s ultimate content tracking tool blog post, by Junio C Hamano, maintainer of Git.
Getting Git to Acknowledge Previously Moved Files
How to make git mark a deleted and a new file as a file move?
How does Git solve the merging problem?

Note: With Git 2.18 (Q2 2018), git status should now show you renames (instead of delete/add files) when you move/rename files.
See "How to tell Git that it s the same directory, just a different name".

友情链接