stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Michal Hocko <mhocko@kernel.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Stable tree <stable@vger.kernel.org>,
	Andy Lutomirski <luto@amacapital.net>,
	Jiri Kosina <jkosina@suse.cz>
Subject: Re: [RFC PATCH] doc: change the way how the stable backport is requested
Date: Mon, 5 Dec 2016 14:15:57 +0100	[thread overview]
Message-ID: <20161205131557.GA23899@1wt.eu> (raw)
In-Reply-To: <20161205130507.GH30758@dhcp22.suse.cz>

Hi Michal,

On Mon, Dec 05, 2016 at 02:05:08PM +0100, Michal Hocko wrote:
> > That's not a problem in that I know I like to see them to give me a
> > "heads up" that something is coming down the pipeline soon.
> 
> Are you really tracking all those discussion to catch resulting patches
> in the Linus' tree? I simply fail to see a point having N versions of
> the patch on the stable mailing list before it gets picked up from the
> _Linus'_ anyayw.
> 
> > I don't think anyone has ever complained of this before, do you?
> 
> This is the reason I have stopped following the stable mailing list.
> The noise level is just too high.

I personally have mixed opinion on this. I agree that there's too much
"noise" on the list, but at the same time I would probably be even more
clueless about patches I receive if I didn't have this noise. As Greg
says, these emails tell you something is coming. For sure I don't keep
track of the discussions nor the threads but sometimes I'm interested
in reading them and that makes my later job easier.

So in the end, I just press ",st" in mutt and all stable mails are moved
away from my mbox and archived into the stable box. My only risk at the
moment is to accidently miss something that people expected me to merge
by sending it to stable only, but that doesn't happen often.

So I think I'm fine with not changing anything as well.

cheers,
Willy

  reply	other threads:[~2016-12-05 13:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-05  7:21 [RFC PATCH] doc: change the way how the stable backport is requested Michal Hocko
2016-12-05 12:52 ` Greg KH
2016-12-05 13:05   ` Michal Hocko
2016-12-05 13:15     ` Willy Tarreau [this message]
2016-12-05 13:24       ` Michal Hocko
2016-12-05 13:30         ` Willy Tarreau
2016-12-05 13:58     ` Greg KH
2016-12-05 14:14       ` Michal Hocko
2016-12-05 14:21         ` Greg KH
2016-12-05 14:39           ` Michal Hocko
2016-12-05 14:43             ` Greg KH
2016-12-05 14:56               ` Michal Hocko

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=20161205131557.GA23899@1wt.eu \
    --to=w@1wt.eu \
    --cc=gregkh@linuxfoundation.org \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=mhocko@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).