AJAX .post异步(AJAX .post async)

 你试过重装你的显示器吗？ 有时gitk有点困惑，但是退出并重新启动它，或者重新加载（ File > Reload或Ctrl - F5 ）可以帮助它以更友好的方式重新绘制历史记录。 
 
 编辑 ：现在我看到了存储库，我可以看到发生了什么。 
 
 看起来你在master上做了一些开发，同时也在一些分支机构上工作。 当你这样做的时候，你将master多次合并到那些side分支中。 gitk在列表中显示提交，因此需要提交的线性排序。 每当您有分支历史记录时，您可以将该历史记录放入几个可能的线性排序。例如，以下结构： 
 
       /-- c -- e --\
a -- b               g -- h
       \-- d -- f --/
 
 可以通过以下任何一种方式订购： 
 
 
 
 a，b，c，e，d，f，g，h 
 
 
 a，b，c，d，e，f，g，h 
 
 
 a，b，c，d，f，e，g，h 
 
 
 a，b，d，c，e，f，g，h 
 
 
 a，b，d，c，f，e，g，h 
 
 
 a，b，d，f，c，e，g，h 
 
 
 默认情况下， gitk使用拓扑排序，它尝试将每个分支上的提交组合在一起，这样您就可以看到每个分支的提交的逻辑进程，而不是根据它们发生的时间散布分支的每一侧的提交。 因此，例如，它可能会在排序中显示它们（1）： 
 
a -- b -- c -- e ------------ g -- h
       \----------- d -- f --/
 
 如果您只是查看线性日志，这种排序可以正常工作，如果您不经常在分支之间进行合并，也可以在gitk正常工作（如给出的示例中所示）。 但是如果你做了你做的事情，经常将master合并到主题分支中，那么这会产生你所看到的那种混乱; 首先显示master上的提交，然后显示侧支路上的提交，但是master频繁地合并到侧支路中会成为堆积起来的长连接并使历史看起来令人困惑。 （请注意，Git实际上并不存储哪个提交来自哪个分支，但是它对它们进行排序的方式最终将每个分支的提交保持在一起，看起来如此）。 
 
 我知道的最简单的处理方法就是按时间顺序显示gitk中的提交。 打开视图 > 编辑视图... ，然后选中严格按日期排序选项。 现在您应该看到您的历史显示得更加清晰。 要直接启动到此视图，您可以将--date-order选项传递给gitk 。 

Have you tried reloading your display? Sometimes gitk gets a bit confused, but quitting and restarting it, or reloading (File > Reload, or Ctrl-F5) can help it re-draw the history in a more friendly fashion.
 
edit: Now that I see the repository, I can see what's going on.
 
It looks like you did some development on master, while also working on some side branches. While you were doing this, you merged master into those side branches several times. gitk displays commits in a list, so it needs a linear ordering of commits. Whenever you have branching history, there are several possible linear orderings you can put that history in. For instance, the following structure:
 
       /-- c -- e --\
a -- b               g -- h
       \-- d -- f --/
 
Could be ordered an any of the following ways:
 
 
 
a, b, c, e, d, f, g, h
 
 
a, b, c, d, e, f, g, h
 
 
a, b, c, d, f, e, g, h
 
 
a, b, d, c, e, f, g, h
 
 
a, b, d, c, f, e, g, h
 
 
a, b, d, f, c, e, g, h
 
 
By default, gitk uses a topological ordering, which tries to group together commits on each branch, so you can see a logical progression of commits for each branch, rather than commits of each side of the branch interspersed based on when they happened. So, for instance, it might display them in ordering (1):
 
a -- b -- c -- e ------------ g -- h
       \----------- d -- f --/
 
This ordering works fine if you're just looking at a linear log, and also works fine in gitk if you don't merge between the branches very often (as in the example given). But if you do what you did, merging master into the topic branches frequently, then this produces the kind of mess that you're seeing; the commits on master are shown first, then the commits on the side branches, but the frequent merging of master into the side branches become the long connections that pile up and make the history look confusing. (Note that Git doesn't actually store which commits came from which branch, but the way it sorts them it winds up keeping the commits from each branch together, it appears).
 
The easiest way to deal with this that I know of is just to display commits in gitk in chronological order. Open View > Edit view..., and check the Strictly sort by date option. Now you should see your history displayed much more sanely. To launch directly into this view, you can pass the --date-order option into gitk.