From: Greg KH <gregkh@linuxfoundation.org>
To: Laura Abbott <labbott@redhat.com>
Cc: ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Bug reporting feedback loop
Date: Fri, 23 Jun 2017 22:52:29 +0800 [thread overview]
Message-ID: <20170623145229.GB1855@kroah.com> (raw)
In-Reply-To: <1de3c642-a4b7-1065-5c35-ba32866d471d@redhat.com>
On Wed, Jun 21, 2017 at 03:34:11PM -0700, Laura Abbott wrote:
> - There's still a gap between when bugs hit Linus' tree and when
> stable releases come out. This is not a knock against stable or
> a request for stable to go faster :). I try
> and monitor stable@ for fixes but there still seems to be a
> large time gap for identifying fixes that have been fixes in
> master that are relevant to a recent stable release.
Ok, I'll bite, what exactly do you mean by "large time"? During the
-rc1 merge window, it can take a few weeks for me to catch up with the
large onslaught of patches marked for stable, but almost all of those
were determined by the develoers to not be all-so-serious, as they were
delayed in getting to Linus for -rc1, and not before.
You can always email and ask for specific patches to be queued up now,
as I go through the list in a semi-random manner.
After the big -rc1 chunk of patches are merged, it's usually only a week
at most before the patches hit a stable release, people usually complain
it goes too fast, not that it's too slow these days.
thanks,
greg k-h
next prev parent reply other threads:[~2017-06-23 14:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 22:34 [Ksummit-discuss] [MAINTAINERS SUMMIT] Bug reporting feedback loop Laura Abbott
2017-06-22 12:36 ` Jiri Kosina
2017-06-27 17:53 ` Luis R. Rodriguez
2017-06-27 18:26 ` Laurent Pinchart
2017-06-27 18:30 ` James Bottomley
2017-06-27 18:41 ` Daniel Vetter
2017-06-27 19:02 ` Luis R. Rodriguez
2017-06-27 19:46 ` Guenter Roeck
2017-06-28 10:19 ` Mark Brown
2017-06-27 22:35 ` Jiri Kosina
2017-06-28 6:59 ` Takashi Iwai
2017-06-27 18:31 ` Takashi Iwai
2017-06-27 19:04 ` Luis R. Rodriguez
2017-06-28 8:04 ` Daniel Vetter
2017-06-22 14:08 ` Takashi Iwai
2017-06-22 14:12 ` Jiri Kosina
2017-06-22 14:24 ` Takashi Iwai
2017-06-28 13:12 ` Jani Nikula
2017-06-28 13:13 ` Takashi Iwai
2017-06-22 15:34 ` James Bottomley
2017-06-23 14:52 ` Greg KH [this message]
2017-06-23 20:28 ` Jiri Kosina
2017-06-25 17:11 ` Laura Abbott
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170623145229.GB1855@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=labbott@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.