[Ksummit-2012-discuss] [ATTEND] stable-kernel git management?
irosen at gmail.com
Wed Jun 20 15:07:26 UTC 2012
Having a linux-stable.git "preview" branch wouldn't hurt, if only to make upcoming changes easier to see. We'd also see the patches getting reverted/removed as that happened if it happened pre-master-merge.
On Jun 20, 2012, at 9:13, Takashi Iwai <tiwai at suse.de> wrote:
> At Wed, 20 Jun 2012 09:02:32 -0400,
> Josh Boyer wrote:
>> On Wed, Jun 20, 2012 at 02:33:32PM +0200, Takashi Iwai wrote:
>>> I'd like to join this year's kernel summit. I can bring expertise
>>> from the sound subsystem maintenance and raise issues learned from the
>>> Linux laptop / desktop preload experiences.
>>> Like many people have already commented on stable kernel process, I'm
>>> also interested in it. Especially whether it makes sense to allow
>>> maintainers to send pull requests to Greg and others.
>>> Currently, we receive patch bombs from Greg when patches are queued or
>>> in the review phase before the stable release. But it's hard to
>>> follow whether all necessary patches are merged only from these
>>> individual patch mails. I often loose some overview.
>>> After all, it's the subsystem maintainer who knows well about the
>>> commits they did, what should be applied to which kernel and how.
>>> I'm willing to do the backport or merge to the stable kernel for my
>>> own commits at the same time I commit to the for-linus branch, then
>>> give Greg to pull.
>> Dave Miller does this for the net tree already, though I don't think it
>> is a pull request. I believe he queues the patches he feels are
>> necessary and then sends them in one large patch.
> OK, that's good to know.
>> That sounds like something any maintainer could ask Greg to work from.
> Yeah, but a general guideline would be good to have, IMO.
>>> This also helps in some cases where the patch is not trivial to
>>> backport. So far, I prepare an extra patch and send to stable after
>>> merge to Linus tree, but I forget often due to this delay.
>>> Or, at least, if we can have the expanded to-be-released-as-stable
>>> git tree, it'd help the review for me...
>> Greg keeps the unreleased patches in a quilt series in the stable-queue
>> git tree. Is that not sufficient? If not, why?
> Well, it's no expanded tree. I'm just too lazy to do "get the latest
> linux-stable.git, update stable-queue.git, apply series" at each time
> Ksummit-2012-discuss mailing list
> Ksummit-2012-discuss at lists.linux-foundation.org
More information about the Ksummit-2012-discuss