Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> writes: > I recently ran across this strange behavior in the gitweb server at > git.kernel.org. The following URL: > > http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.27.y.git;a=commit;h=2d93148ab6988cad872e65d694c95e8944e1b62 > > brings up a page containing commit 2d93148[...]. But that commit isn't > part of the 2.6.27.y tree! It belongs to Linus's main tree, and it was > added long after 2.6.27.y was forked off. The actual commit applied to > 2.6.27.y was 070bb0f3b6df167554f0ecdeb17a5bcdb1cd7b83. > > So what's going on here? Nothing mysterious. Every tree on kernel.org borrows from Linus' main tree via .git/objects/info/alternates, thus includes its whole object database by reference. Andreas. -- Andreas Schwab, schwab@xxxxxxxxxxxxxx GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html