From: Jiri Kosina <jikos@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Bug reporting feedback loop
Date: Fri, 23 Jun 2017 22:28:28 +0200 (CEST) [thread overview]
Message-ID: <alpine.LSU.2.20.1706232226370.30709@cbobk.fhfr.pm> (raw)
In-Reply-To: <20170623145229.GB1855@kroah.com>
On Fri, 23 Jun 2017, Greg KH wrote:
> 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.
I agree, we don't see the pace at which patches make it into -stable as a
big issue for us (*); in case we need anything cherry-picked from Linus'
tree earlier than it appears in -stable, we just do that, and drop it from
our tree once we merge new -stable.
(*) sometimes it's actually quite the contrary :)
Thanks,
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2017-06-23 20:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 22:34 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
2017-06-23 20:28 ` Jiri Kosina [this message]
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=alpine.LSU.2.20.1706232226370.30709@cbobk.fhfr.pm \
--to=jikos@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox