Not only that, it's even a Bitcoin commit:
https://github.com/bitcoin/bitcoin/commit/40149c4e41114499c324abc313aea93a59bfa2f7 :smile:
That's most probably the way Git commits are chained together.
When you go bottom up from the very first Bitcoin commit you will stay at the same master branch until it ends at the very last Bitcoin(!) commit. Somewhere on the way up there was a fork to Litecoin, later on from Litecoin to Darkcoin/Dash.
When you go top-down (Dash -> Litecoin -> Bitcoin, just click on each "parent" commit) you go down to the very first Darkcoin commit, it's parent is the latest Litecoin commit before(!) the fork, then you'll come to the very first Litecoin commit, it's parent is the latest Bitcoin commit before the fork.
The links above just show how the Bitcoin/Litecoin commit chain would look when you follow those forks.
I guess the advantage to do it this way is that it makes things easier when you merge a fork (which itself is a repository) down to the original repository, you can still verify whether both are identical or different.
Example: I have my own fork of Dash here:
https://github.com/crowning-/dash
I named it Dash, but I could also have renamed it to
CrowningCoin or whatever else. When I develop new features, Git can easily keep track of a) what I have changed, and b) what has changed in the original repository.
This is important, because if Evan would change something in the original Dash repository I can easily check whether it would collide with my changes or not. The opposite way also works, when I change things Git can easily find out whether my changes can be automatically be merged back into Evan repository or if I have to adjust my developments to stay compatible.
You can see ALL of Evan's commits under my repository also:
https://github.com/crowning-/dash/commit/40149c4e41114499c324abc313aea93a59bfa2f7
Sounds complicated, but saves a ton of work.