Strange behavior of gitweb

If this isn't the right place to post this, could somebody please let 
me know where would be better?

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?  Shouldn't the correct behavior be to report
an error, since the requested commit isn't in the history of the
specified tree?

Thanks,

Alan Stern