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.
All other commits in this range had been done on 3.4.0 and less:
35916acedd8dadb361ef6439d05d60fbe8f53032 (dated May 31)
and all earlier commits have been done on 3.4.0 and its rc builds.
As the issue is NOT present in the 3.4.x series anyway, I assume that only the two commits on 3.5.0-rc4 above (if any) from this interval are relevant, and we rather need to look at the subsequent v3.5..v3.6 range!?
Am I correct (and please bear with me in case I got it wrong - I had never used git before looking into this...)?
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:
9bd0c15fcfb42f6 245447c53347d65 ad9e72080b (dated Jun 26, 2012) and 6c168ef58ee7d48 90545ede1c (dated Jun 27)
e9bf5f36b09f8ec
when looking at the global Makefile:
git show <commit- sha1>:Makefile
have been done on 3.5.0-rc4 version of the kernel.
All other commits in this range had been done on 3.4.0 and less:
35916acedd8dadb 361ef6439d05d60 fbe8f53032 (dated May 31)
and all earlier commits have been done on 3.4.0 and its rc builds.
As the issue is NOT present in the 3.4.x series anyway, I assume that only the two commits on 3.5.0-rc4 above (if any) from this interval are relevant, and we rather need to look at the subsequent v3.5..v3.6 range!?
Am I correct (and please bear with me in case I got it wrong - I had never used git before looking into this...)?
Thanks & BR,
Andreas