From: Willy Tarreau <w@1wt.eu>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "Levin, Alexander" <alexander.levin@verizon.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"jslaby@suse.cz" <jslaby@suse.cz>,
"ben@decadent.org.uk" <ben@decadent.org.uk>,
"kamal@canonical.com" <kamal@canonical.com>,
"dchinner@redhat.com" <dchinner@redhat.com>
Subject: Re: stable commit notes
Date: Wed, 24 Aug 2016 22:46:32 +0200 [thread overview]
Message-ID: <20160824204632.GA24356@1wt.eu> (raw)
In-Reply-To: <20160824201638.GA2133@kroah.com>
On Wed, Aug 24, 2016 at 04:16:38PM -0400, gregkh@linuxfoundation.org wrote:
> On Wed, Aug 24, 2016 at 03:38:39PM +0200, Willy Tarreau wrote:
> > On Wed, Aug 24, 2016 at 09:15:26AM -0400, Levin, Alexander wrote:
> > > On Wed, Aug 24, 2016 at 02:34:07AM -0400, Willy Tarreau wrote:
> > > > Hi Sasha,
> > > >
> > > > On Tue, Aug 23, 2016 at 01:54:40PM -0400, Levin, Alexander wrote:
> > > > > I've decided to automate the bits I had for tracking stable mailing list
> > > > > discussion and wrap it into the git notes interface to make it easy for
> > > > > stable maintainers to track discussions related to stable commits.
> > > >
> > > > I actually think it's a good idea. I already use notes locally when I
> > > > know I have to take care of certain commits, or when I want to mark that
> > > > I already tested them. I don't know how practical this will be over the
> > > > long term but it can definitely help.
> > >
> > > What's the concern about long term? My view is that if this will encourage
> > > reviews in the long term.
> >
> > I'm not saying I have a concern, all I'm saying is that ideas which sound
> > good initially have to prove good over time, that's all. You can ask Greg,
> > the stable maintenance process has evolved quite a bit over the last 8 years
> > (and that's for good).
>
> Hah, if only it were "8", it's been 11 from my count. The "first"
> stable kernel I released was 2.6.11.1 back on March 4, 2005.
You're right, I only started to count with the first LTS, I must
be a bit tainted :-)
> time flies...
Oh yes, I just noticed that my first "official" 2.4.33.1 was exactly
10 years ago!
Willy
prev parent reply other threads:[~2016-08-24 20:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160823175440.GA4182@sasha-lappy>
2016-08-24 6:34 ` stable commit notes Willy Tarreau
[not found] ` <20160824131526.GA7184@sasha-lappy>
2016-08-24 13:38 ` Willy Tarreau
2016-08-24 20:16 ` gregkh
2016-08-24 20:46 ` Willy Tarreau [this message]
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=20160824204632.GA24356@1wt.eu \
--to=w@1wt.eu \
--cc=alexander.levin@verizon.com \
--cc=ben@decadent.org.uk \
--cc=dchinner@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=kamal@canonical.com \
--cc=stable@vger.kernel.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