https://bugs.freedesktop.org/show_bug.cgi?id=58378

--- Comment #36 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
(In reply to comment #35)
> Follow-up question note that I am digging deeper into git... ;-)
> 
> From the commits in the v3.4..v3.5 range, only two of them:
> 
> 9bd0c15fcfb42f6245447c53347d65ad9e72080b (dated Jun 26, 2012) and
> e9bf5f36b09f8ec6c168ef58ee7d4890545ede1c (dated Jun 27)
> 
> when looking at the global Makefile:
> 
> git show <commit-sha1>:Makefile
> 
> have been done on 3.5.0-rc4 version of the kernel.

Most assuredly not the right way to look at it.

> 
> All other commits in this range had been done on 3.4.0 and less:
> 
> 35916acedd8dadb361ef6439d05d60fbe8f53032 (dated May 31)

And of course date of the commit has nothing to do with anything either.

Think about the branched development model. Let's say I do some work, basing my
work on, say, 2.6.0. I spend a lot of time on it. Then I send a pull request to
Linus (or whoever). He merges it. When looking at my commits, you might think
that you're looking at a 2.6.0 kernel, based on the Makefile. And in a large
sense you are. But in reality the commits were merged into some much later
release. Same with dates.

You can either read about git and fully understand it, or you can kinda trust
that the tools aren't lying to you when you ask for a bisect in a range, or a
log of commits between two revisions.

-- 
You are receiving this mail because:
You are the assignee for the bug.