Mercurial 可以使用更好的 diff 工具来更有效地存储其变更集吗？
我使用 TortoiseHg 来提交更改。提交对话框中显示的（默认）差异包含大量添加/删除。
但相比之下，当我单击提交对话框中的 diff 图标时，KDiff3 将打开，并且该比较更加“智能”：它检测到我更改的“更好”内容：我移动了一段代码，从而减少了很多添加/删除。
由于 Hg "...存储将旧版本转换为所需的更改新版本。”，我想知道是否可以利用 KDiff3 的“智能”将这些更改存储在 Hg 提交中？
另一个问题中提出的解决方案似乎并不存在应用于 TortoiseHg 提交对话框。
提前致谢！
I use TortoiseHg to commit changes. The (default) diff that is shown in the commit dialog contains a lot of additions/deletions.
But in contrast when I click on the diff icon in the commit dialog, KDiff3 opens and that comparison is a lot more 'intelligent': it detects 'better' what I changed: I moved a block of code, resulting in a lot less additions/deletions.
Since Hg "...stores the changes needed to transform an older revision into the new revision.", I was wondering if I could make use of the 'intelligence' of KDiff3 to store these changes in an Hg commit?
The proposed solution in another question doesn't seem to apply to the TortoiseHg commit dialog.
Thanks in advance!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
事实证明我误解了 hg commit 的行为。
提交时使用内部
hg diff命令或 KDiff3 查看更改并不重要：然而，在合并时，KDiff3 的智能仍然可以使用。
As it turns out I misunderstood the behavior of
hg commit.It doesn't matter if you look at changes with the internal
hg diffcommand or with KDiff3 when committing:At merge time however, the intelligence of KDiff3 can still be used.