blocks|key|947986|text|你不能真的做到这一点。git中的历史是一个directed+acyclic+graph+-每次提交都包含对其父级的引用，但父级没有对其子级的引用。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|947987|当您考虑创建多个分支的提交时，这里的问题应该变得显而易见。你指的是哪个“下一次提交”？对于parents，您可以关闭(正常的合并提交有第一个和第二个父级)，但是如何对子进程执行此操作？即使你知道你试图在哪个分支上(例如，你已经签出了master~4，现在你想看看master~3)，它的定义也不是很好--你可能会遇到这样的情况：|style|CODE|947988|-+X+(HEAD)+-+o+-+o+-+o+-+Y+(master)
+++\++++++++++++++++++++/
++++o+-+o+-+o+----------|code-block|syntax|javascript|947989|也就是说，在简单的情况下，您可以这样做：|947990|git+checkout+$(git+rev-list+HEAD..master+%7C+tail+-n+1)|947991|显然，对于线性历史，这将很好地工作。合并..。rev-list在历史上从现在到过去工作，向后追随它。我认为它首先跟随第一个父代，所以最后打印的东西将是通过跟随所有最后的父代找到的HEAD之后的提交。|947992|编辑:这确实假设您知道要前进到哪个分支。如果你不这样做..。好吧，你很可能会在所有的引用中寻找以当前头作为父对象的提交--可能是对git+rev-parse的输出|947993|git+rev-list+--all+--children+%7C+grep+%5E$(git+rev-parse+HEAD)|947994|然后从行中抓取另一个SHA1+(使用awk，随便什么)。但是，如果有多个结果，您将不得不手动检查或做出任意选择。|947995|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Directed_acyclic_graph^0|L|M|0|0|38|8|3N|8|0|0|0|0|N|8|2H|4|0|1T|D|0|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@$A|17|B|18|1|19]]|C|$]]|$1|D|3|E|5|6|7|1A|8|@$A|1B|B|1C|F|G]|$A|1D|B|1E|F|G]]|9|@]|C|$]]|$1|H|3|I|5|J|7|1F|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|1G|8|@]|9|@]|C|$]]|$1|O|3|P|5|J|7|1H|8|@]|9|@]|C|$K|L]]|$1|Q|3|R|5|6|7|1I|8|@$A|1J|B|1K|F|G]|$A|1L|B|1M|F|G]]|9|@]|C|$]]|$1|S|3|T|5|6|7|1N|8|@$A|1O|B|1P|F|G]]|9|@]|C|$]]|$1|U|3|V|5|J|7|1Q|8|@]|9|@]|C|$K|L]]|$1|W|3|X|5|6|7|1R|8|@]|9|@]|C|$]]|$1|Y|3|-4|5|6|7|1S|8|@]|9|@]|C|$]]]|Z|$10|$5|11|12|13|C|$14|15]]]]

You can't really do precisely that. History in git is a <a href="https://en.wikipedia.org/wiki/Directed_acyclic_graph" rel="nofollow noreferrer">directed acyclic graph</a> - each commit contains references to its parents, but parents don't have references to their children.

The problem here should become obvious when you think about a commit you created multiple branches from. Which "next commit" do you mean? With parents, you can number off (a normal merge commit has a first and second parent), but how do you do that with children? Even if you know what branch you're trying to be on (e.g. you've checked out <code>master~4</code> and now you want to look at <code>master~3</code>) it's not well-defined - you could be in a situation like this:

<pre><code>- X (HEAD) - o - o - o - Y (master)
 \ /
 o - o - o ----------
</code></pre>

That said, in simple cases, you could do something like this:

<pre><code>git checkout $(git rev-list HEAD..master | tail -n 1)
</code></pre>

Clearly that'll work fine with linear history. With merges... <code>rev-list</code> works from present to past in the history, following it backward. I believe it follows the first parent first, so the thing printed last will be the commit after <code>HEAD</code> found by following all last parents.

Edit: That does assume that you know which branch you want to move forward toward. If you don't... well, you're pretty much stuck looking on all refs for commits which have the current HEAD as parent - probably grepping the output of <code>git rev-parse</code>:

<pre><code>git rev-list --all --children | grep ^$(git rev-parse HEAD)
</code></pre>

Then grab the other SHA1 from the line (use awk, whatever). You'll have to manually inspect or make an arbitrary choice if there are multiple results though...

blocks|key|948058|text|据我所知，没有象征性的方式来引用提交的子对象。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|948059|我现在能给你的最好的就是git+rev-list的--children选项。在这里，我要求将最近的四个承诺打印得很漂亮，以及关于他们孩子的信息。请注意，在每个条目(不是最近的条目)的"+commit“行上有一个额外的提交编号，它指定该节点的子节点。您可以手动获取它，也可以通过一些shell脚本获取该子对象。|offset|length|style|CODE|948060|$+git+rev-list+--children+--pretty+HEAD~3...

commit+20dba296ad1d48ec90f9319e2c13b245e849f698
Author:+Somebody+<____@____.net>
Date:+++Thu+May+6+19:10:38+2010+-0400

++++Support+for+complex+trig/pow.

commit+9d42b5bac1721a847a39c25672e577c7101c8ff0+20dba296ad1d48ec90f9319e2c13b245e849f698
Author:+Somebody+<____@____.net>
Date:+++Wed+May+5+21:55:07+2010+-0400

++++Fix+doc+formatting+warning.

commit+72bed3baa9df71cb224dfa8388b5969d50f5567c+9d42b5bac1721a847a39c25672e577c7101c8ff0
Merge:+b8244cb61491c9cdb83d36e57f8eb49773e44f6b+899c3dd3f9f419f200b84ca0abe59d7ac3d5bb53
Author:+Somebody+<____@____.net>
Date:+++Wed+May+5+21:54:59+2010+-0400

++++Merge+branch+'master'+

commit+899c3dd3f9f419f200b84ca0abe59d7ac3d5bb53+72bed3baa9df71cb224dfa8388b5969d50f5567c
Author:+Somebody+<____@____.net>
Date:+++Wed+May+5+21:19:11+2010+-0400

++++Fix+link|code-block|syntax|javascript|948061|entityMap^0|0|C|C|P|A|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@$D|Q|E|R|F|G]|$D|S|E|T|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|U|8|@]|9|@]|A|$K|L]]|$1|M|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|N|$]]

As far as I can tell there's no symbolic way to refer to the children of a commit. 

The best I can give you just now is the <code>--children</code> option of <code>git rev-list</code>. Here I ask for the four most recent commits to be pretty-printed, plus information on their children. Note that on the "commit" line of each entry (other than the most recent) there is an extra commit number, which specifies the child of that node. You could grab that either manually or through some shell scripting to get to the child.

<pre><code>$ git rev-list --children --pretty HEAD~3...

commit 20dba296ad1d48ec90f9319e2c13b245e849f698
Author: Somebody &lt;____@____.net&gt;
Date: Thu May 6 19:10:38 2010 -0400

 Support for complex trig/pow.

commit 9d42b5bac1721a847a39c25672e577c7101c8ff0 20dba296ad1d48ec90f9319e2c13b245e849f698
Author: Somebody &lt;____@____.net&gt;
Date: Wed May 5 21:55:07 2010 -0400

 Fix doc formatting warning.

commit 72bed3baa9df71cb224dfa8388b5969d50f5567c 9d42b5bac1721a847a39c25672e577c7101c8ff0
Merge: b8244cb61491c9cdb83d36e57f8eb49773e44f6b 899c3dd3f9f419f200b84ca0abe59d7ac3d5bb53
Author: Somebody &lt;____@____.net&gt;
Date: Wed May 5 21:54:59 2010 -0400

 Merge branch 'master' 

commit 899c3dd3f9f419f200b84ca0abe59d7ac3d5bb53 72bed3baa9df71cb224dfa8388b5969d50f5567c
Author: Somebody &lt;____@____.net&gt;
Date: Wed May 5 21:19:11 2010 -0400

 Fix link
</code></pre>

In git, I can specify the previous revision by saying <code>HEAD^</code> or <code>HEAD~1</code>. What about going the other way? Suppose I'm on revision X, and I do <code>git checkout X^</code>. How do I go back?

Something like <code>git checkout X+</code>?

What is the opposite of `git diff HEAD^`?

在git中，我可以通过说HEAD^或HEAD~1来指定以前的版本。走另一条路怎么样？假设我使用的是修订版X，并且我使用git checkout X^。我该怎么回去呢？像git checkout X+这样的东西

问‘`git diff HEAD^’的反义词是什么？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问‘`git diff HEAD^’的反义词是什么？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问‘`git diff HEAD^’的反义词是什么？
EN