Pulling doesn't change the SHA1 ID of a commit, so _if_ it had been stable
in the -mmc tree, it would have had the same commit in the kernel too.
That's very much a design issue in git: the same commit always has the
same ID. _ALWAYS_.
So the fact that the ID changed implies that something odd happened in the
-mmc tree. Most likely a rebase. And again, this implies that somebody
rebased already-public commits, since otherwise nobody would have ever
even seen the original SHA1 ID.
Which is not good behaviour, _exactly_ because it makes it much harder for
people to work together - suddenly a commit that got reported (for
whatever reason: bug-report or 'please backport', it's all the same issue
in the end) no longer exists.
Linus
--
