[Ksummit-discuss] [CORE TOPIC] stable workflow

Dmitry Torokhov dmitry.torokhov at gmail.com
Mon Jul 11 17:15:06 UTC 2016


On Mon, Jul 11, 2016 at 01:03:33PM -0400, Theodore Ts'o wrote:
> On Mon, Jul 11, 2016 at 04:13:00PM +0100, Mark Brown wrote:
> > On Sat, Jul 09, 2016 at 05:21:30PM -0400, Theodore Ts'o wrote:
> > 
> > > the latest stable kernel.  (But even if they do, apparently many
> > > device vendors aren't bothering to merge in changes from the SOC's BSP
> > > kernel, even if the BSP kernel is getting -stable updates.)
> > 
> > It would be pretty irresponsible for device vendors to be merging BSP
> > trees, they're generally development things with ongoing feature updates
> > that might interact badly with things the system integrator has done
> > rather than something stable enough to just merge constantly.
> 
> So the question is who actually uses -stable kernels,

Community-based distros definitely use stable, but that might be the
latest stable, not the older stables that are out there.

> and does it make
> sense for it even to be managed in a git tree?
> 
> Very few people will actually be merging them, and in fact maybe
> having a patch queue which is checked into git might actually work
> better, since it sounds like most people are just cherry-picking
> specific patches.

Cherry picking a commit from a branch/remote is much nicer than fetching
a part of [quilt based?] patch queue from git, unless I misunderstand
what you are proposing.

Thanks.

-- 
Dmitry


More information about the Ksummit-discuss mailing list