Re: Kernel development cycle
- Date: Thu, 10 Aug 2017 07:37:26 +0200
- From: solitone <solitone@xxxxxxxx>
- Subject: Re: Kernel development cycle
On Tuesday, 1 August 2017 14:15:52 CEST solitone wrote:
> Let's consider a practical example, the history of patch
> "drm/i915/execlists: Reset RING registers upon resume". This patch was
> committed 641 commits after version 4.8-rc2:
> $ git describe bafb2f7d4755bf1571bd5e9a03b97f3fc4fe69ae
> So I would expect to find it in version 4.8, which is the stable, final
> release of v4.8, following all the release canditates.
> However, if I search for the tag that follows (and hence contains) that
> commit, I do not find version 4.8, nor version 4.9, but 4.10:
> $ git describe --contains bafb2f7d4755bf1571bd5e9a03b97f3fc4fe69ae
> Why? Why not v4.8-rc3? This means that the patch has been included neither
> in v4.8 nor in v4.9, but only in version 4.10-rc1, right? Why so much time
> was needed, considering it was the 621st commit on top ov v4.8-rc2?
Could you please point me out some doc that might help me understand this? I'm
still thinking about it!
⣾⠁⢠⠒⠀⣿⡁ Sent from my brain using neurons fueled by glucose.