blocks|key|2375916|text|简短的回答，那是不可能的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2375917|来自亚特兰西安的Git教程|offset|length|2375918|修改后的提交实际上是全新的提交，以前的提交将不再在当前分支上。|blockquote|2375919|也就是说，您将无法访问修改后的提交。|2375920|作为另一种选择，您可以将所有更改作为单独的提交来应用，并且在完成评审后，可以使用果汁+(第一部分:压缩提交)使用交互重基应用它们。|2375921|entityMap|0|LINK|mutability|MUTABLE|url|https://www.atlassian.com/git/tutorials/rewriting-history|1|https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History|2|https://git-scm.com/docs/git-rebase^0|0|2|B|0|0|0|0|14|2|1|1K|4|2|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@$D|10|E|11|1|12]]|A|$]]|$1|F|3|G|5|H|7|13|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|14|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|15|8|@]|9|@$D|16|E|17|1|18]|$D|19|E|1A|1|1B]]|A|$]]|$1|M|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]|U|$5|P|Q|R|A|$S|V]]|W|$5|P|Q|R|A|$S|X]]]]

Short answer, that is not possible.

From <a href="https://www.atlassian.com/git/tutorials/rewriting-history" rel="nofollow noreferrer">Atlassian's Git Tutorials</a>:

<blockquote>
 Amended commits are actually entirely new commits and the previous commit will no longer be on your current branch. 
</blockquote>

That is, you won't be able to access amended commits.

As an alternative, you could apply all changes as separate commits and when you finished the review <a href="https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History" rel="nofollow noreferrer">squash</a> (section: Squashing commits) them using <a href="https://git-scm.com/docs/git-rebase" rel="nofollow noreferrer">interactive rebase</a>.

blocks|key|2375935|text|假设所有“修正”都有相同的更改-ID，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2375936|(这就是Gerrit将一组提交与同一Gerrit-更改相关联的方式，|2375937|您可以选择要与彼此进行比较的更改的版本。|2375938|默认行为是将基(集合中的第一次提交)与最新的+one进行比较。|offset|length|style|BOLD|2375939|在本地(git-)分支中，还可以看到更改的不同版本。|2375940|通过使用git+reflog命令。|CODE|2375941|(git+reflog像面包屑一样显示了您的工作历史，|2375942|您甚至可以使用show和cherry-pick来修改这些版本)|2375943|entityMap^0|0|0|0|6|1|J|3|0|0|4|A|0|1|A|0|7|4|C|B|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Z|8|@$H|10|I|11|J|K]|$H|12|I|13|J|K]]|9|@]|A|$]]|$1|L|3|M|5|6|7|14|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|15|8|@$H|16|I|17|J|P]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|18|8|@$H|19|I|1A|J|P]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1B|8|@$H|1C|I|1D|J|P]|$H|1E|I|1F|J|P]]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|V|$]]

Assuming all "amendments" have the same Change-ID, 
(which is how Gerrit associates a set of commits to the same Gerrit-Change, 
you can choose which versions of a change you would like to compare to each-other. 

The default behavior is to compare the Base (first commit in the set) to the latest one. 

In your local (git-)branch, you could also see the different versions of your change 
by using the <code>git reflog</code> command. 

(<code>git reflog</code> shows the history of your work like breadcrumbs, 
and you can even <code>show</code> and <code>cherry-pick</code> any of those revisions)

blocks|key|739863|text|如果所有的修改都有相同的Change-Id，那么这些都是一个更改的补丁集。您没有在问题中指定diff是如何显示的，因此以下是可能的解决方案之一。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|739864|ssh+-p+<port>+<username>@<gerrithost>+gerrit+query+commit:<commit-id>+--patch-sets+--format=json|code-block|syntax|javascript|739865|默认情况下，port为29418；|unordered-list-item|739866|username是运行gerrit+query的gerrit用户名。应对阅览资料库参考文献的权利进行评估；|739867|gerrithost是您gerrit的主机名或IP地址；|739868|commit-id是commit的sha1值。|739869|--format=json是可选的。默认格式是text。|739870|输出包括有关更改的修补程序集的详细信息，包括如下条目：|739871|ref:+refs/changes/90/812290/3
ref:+refs/changes/90/812290/2
ref:+refs/changes/90/812290/1|739872|这些是Gerrit为每个被推送到refs/for目的地的提交创建的参考资料。如果您知道数字812290，您可以使用change:812290替换gerrit+query中的commit:<commit-id>。在本地存储库中获取这些参考资料：|739873|git+fetch+origin+refs/changes/90/812290/3|739874|这些参考文件所指向的提交将被下载，然后您可以运行git命令来任意操作它们。|739875|git+diff+commit1+commit2|739876|您可以在Gerrit的文档中搜索gerrit+query以了解更多信息。|739877|entityMap^0|C|9|0|0|6|4|0|0|8|B|C|0|0|A|0|0|9|0|0|D|N|4|0|0|0|G|8|19|6|1L|D|20|C|2E|I|0|0|0|0|G|C|0^^$0|@$1|2|3|4|5|6|7|1B|8|@$9|1C|A|1D|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|1E|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|M|7|1F|8|@$9|1G|A|1H|B|C]]|D|@]|E|$]]|$1|N|3|O|5|M|7|1I|8|@$9|1J|A|1K|B|C]|$9|1L|A|1M|B|C]]|D|@]|E|$]]|$1|P|3|Q|5|M|7|1N|8|@$9|1O|A|1P|B|C]]|D|@]|E|$]]|$1|R|3|S|5|M|7|1Q|8|@$9|1R|A|1S|B|C]]|D|@]|E|$]]|$1|T|3|U|5|M|7|1T|8|@$9|1U|A|1V|B|C]|$9|1W|A|1X|B|C]]|D|@]|E|$]]|$1|V|3|W|5|6|7|1Y|8|@]|D|@]|E|$]]|$1|X|3|Y|5|H|7|1Z|8|@]|D|@]|E|$I|J]]|$1|Z|3|10|5|6|7|20|8|@$9|21|A|22|B|C]|$9|23|A|24|B|C]|$9|25|A|26|B|C]|$9|27|A|28|B|C]|$9|29|A|2A|B|C]]|D|@]|E|$]]|$1|11|3|12|5|H|7|2B|8|@]|D|@]|E|$I|J]]|$1|13|3|14|5|6|7|2C|8|@]|D|@]|E|$]]|$1|15|3|16|5|H|7|2D|8|@]|D|@]|E|$I|J]]|$1|17|3|18|5|6|7|2E|8|@$9|2F|A|2G|B|C]]|D|@]|E|$]]|$1|19|3|-4|5|6|7|2H|8|@]|D|@]|E|$]]]|1A|$]]

If all the amendments have the same <code>Change-Id</code>, then thay are patch sets of one change. You don't specify in the question how the diff is displayed, so here's one of the possible solutions.

<pre><code>ssh -p &lt;port&gt; &lt;username&gt;@&lt;gerrithost&gt; gerrit query commit:&lt;commit-id&gt; --patch-sets --format=json
</code></pre>

<ul>
<li><code>port</code> is 29418 by default; </li>
<li><code>username</code> is the gerrit username to run
<code>gerrit query</code>. It should be assinged the right to read the refs of
the repository;</li>
<li><code>gerrithost</code> is the the host name or the IP address of your gerrit;</li>
<li><code>commit-id</code> is the sha1 value of a commit.</li>
<li><code>--format=json</code> is optional. The default format is <code>text</code>.</li>
</ul>

The output includes details about the patch sets of the change, including entries like:

<pre><code>ref: refs/changes/90/812290/3
ref: refs/changes/90/812290/2
ref: refs/changes/90/812290/1
</code></pre>

These are the refs that Gerrit creates for every commit that is pushed to <code>refs/for</code> destination. If you know the number <code>812290</code>, you could use <code>change:812290</code> to replace <code>commit:&lt;commit-id&gt;</code> in the <code>gerrit query</code>. Fetch these refs in a local repository:

<pre><code>git fetch origin refs/changes/90/812290/3
</code></pre>

The commits that are pointed at by these refs are downloaded and then you can run git commands to manipulate them as you like.

<pre><code>git diff commit1 commit2
</code></pre>

You could search for <code>gerrit query</code> in Gerrit's docs to learn more.

blocks|key|739894|text|使用$+git+log+--reflog，就好像重发所提到的所有对象都列在命令行的commit中一样。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|739895|entityMap^0|2|I|15|6|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

Use <code>$ git log --reflog</code> as if all objects mentioned by reflogs are listed on the command line as <code>commit</code>.

So basically, I know that to see past git commits, you do git log. But at my company we work with gerrit on one commit and you make amendments to that commits. How do I see all the past amendments to that specific commit, so I see each of their commit message and I can diff between the amendments? THANKS!

how to git log amendments

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

基本上，我知道要查看过去的git提交，您可以做git日志。但在我的公司，我们和格瑞特一起做了一次承诺，而你对此承诺做出了修改。我如何看待过去对该特定提交的所有修改，所以我看到了它们的每个提交消息，并且我可以在修改之间进行区分？谢谢!

问如何进行git日志修改
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何进行git日志修改EN