All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Greg KH <greg@kroah.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	ksummit-2013-discuss@lists.linuxfoundation.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [Ksummit-2013-discuss] KS Topic request: Handling the Stable kernel, let's dump the cc: stable tag
Date: Tue, 16 Jul 2013 10:10:31 +0400	[thread overview]
Message-ID: <1373955031.2148.18.camel@dabdike> (raw)
In-Reply-To: <20130716000623.GB26261@kroah.com>

On Mon, 2013-07-15 at 17:06 -0700, Greg KH wrote:
> On Mon, Jul 15, 2013 at 06:01:39PM -0400, Steven Rostedt wrote:
> > On Mon, 2013-07-15 at 14:44 -0700, Greg KH wrote:
> > 
> > > I don't like this at all, just for the simple reason that it will push
> > > the majority of the work of stable kernel development on to the
> > > subsystem maintainers, who have enough work to do as it is.
> > > 
> > > Stable tree stuff should cause almost _no_ extra burden on the kernel
> > > developers, because it is something that I, and a few other people, have
> > > agreed to do with our time.  It has taken me 8 _years_ to finally get
> > > maintainers to agree to mark stuff for the stable tree, and fine-tune a
> > > development process that makes it easy for us to do this backport work.
> > 
> > Although, since those 8 years, the stable tree has proven its
> > importance.
> > 
> > Is a extra "ack" also too much to ask?
> 
> Maintainers are our most limited resource, I'm getting their "ack" when
> they themselves tag the patch to be backported with the Cc: line.
> 
> I then cc: them when the patch goes into the patch queue.
> 
> I then cc: them again when the patch is in the -rc1 phase.
> 
> How many times do I need to do this to give people a chance to say
> "nak"?

Just to pick up on this, the problem from my perspective is that this
cc: goes into my personal inbox.  From a list perspective this just
doesn't work.  The entirety of my workflow is set up to operate from the
mailing lists.  My inbox is for my day job.  It gets about 100 emails or
more a day and anything that goes in there and doesn't get looked at for
a day gets lost.  I sometimes feel guilty about seeing stable reviews
whiz by, but not necessarily guilty enough to go back and try to find
them.  I have thought of using filtering to manually place these into a
deferred mailbox for later use.  However, the problem is that my work
inbox is exchange, and the only tags I could filter on seem to be in the
body (exchange does body filtering about as elegantly as a penguin
flies).

That's where the suggestion to drop cc: stable@ came from.  I realise
the workflow just isn't working for me.

I say we have the discussion at KS then I'll investigate a different
workflow for SCSI.

James



  parent reply	other threads:[~2013-07-16  6:10 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-15 19:27 KS Topic request: Handling the Stable kernel, let's dump the cc: stable tag James Bottomley
2013-07-15 19:45 ` [Ksummit-2013-discuss] " Steven Rostedt
2013-07-15 19:55   ` Willy Tarreau
2013-07-15 20:56     ` Steven Rostedt
2013-07-15 21:09       ` Joe Perches
2013-07-15 21:21         ` Steven Rostedt
2013-07-15 21:34           ` Joe Perches
2013-07-21  4:06         ` Rob Landley
2013-07-15 21:52       ` Willy Tarreau
2013-07-15 20:15   ` Mark Brown
2013-07-15 21:07     ` Steven Rostedt
2013-07-15 20:19 ` Guenter Roeck
2013-07-15 22:04   ` David Woodhouse
2013-07-15 22:07     ` Guenter Roeck
2013-07-15 22:38       ` H. Peter Anvin
2013-07-15 23:22         ` Guenter Roeck
2013-07-16  0:13           ` H. Peter Anvin
2013-07-16  0:21             ` Greg KH
2013-07-16  0:25               ` H. Peter Anvin
2013-07-16 15:50                 ` Paul Gortmaker
2013-07-15 20:20 ` Jason Cooper
2013-07-15 21:44 ` Greg KH
2013-07-15 21:55   ` Greg KH
2013-07-15 22:01     ` H. Peter Anvin
2013-07-15 23:08       ` Greg KH
2013-07-16  0:40         ` [Ksummit-2013-discuss] " Rafael J. Wysocki
2013-07-16  9:06       ` Jiri Kosina
2013-07-15 22:01   ` Steven Rostedt
2013-07-16  0:06     ` Greg KH
2013-07-16  2:09       ` Steven Rostedt
2013-07-16  2:41         ` Ben Hutchings
2013-07-16  3:27           ` Dave Airlie
2013-07-16  3:43             ` Steven Rostedt
2013-07-16  4:10             ` Ben Hutchings
2013-07-16  6:23             ` Greg KH
2013-07-16  6:10       ` James Bottomley [this message]
2013-07-16  6:28         ` Greg KH
2013-07-15 22:22   ` Jiri Kosina
2013-07-15 23:40     ` Jiri Kosina
2013-07-15 23:59     ` Greg KH
2013-07-16  2:30   ` Ben Hutchings
2013-07-16  6:13     ` Greg KH
2013-07-16  9:11       ` Jiri Kosina
2013-07-16 16:36         ` Greg KH
2013-07-17  3:53           ` Ben Hutchings
2013-07-17  4:24             ` Greg KH
2013-07-16  5:17   ` James Bottomley
2013-07-16  6:20     ` Greg KH
2013-07-16  7:43       ` [Ksummit-2013-discuss] " James Bottomley
2013-07-16  9:46         ` Jiri Kosina
2013-07-16  9:46           ` Jiri Kosina
2013-07-16 12:43           ` Ben Hutchings
2013-07-16 16:35           ` Greg KH
2013-07-16 23:15             ` Jiri Kosina
2013-07-16 13:14         ` Josh Boyer
2013-07-17 15:08         ` John W. Linville
2013-07-18  7:45           ` Kalle Valo
2013-07-16 10:02       ` Jan Kara
2013-07-16  6:24   ` David Lang
2013-07-16 16:45     ` [Ksummit-2013-discuss] " Steven Rostedt
2013-07-16  2:00 ` Ben Hutchings
2013-07-16  9:53   ` Mark Brown
2013-07-21  4:11 ` Rob Landley
2013-07-21 15:09   ` [Ksummit-2013-discuss] " Ben Hutchings
2013-07-22 21:24     ` KOSAKI Motohiro
2013-07-23  2:29       ` Li Zefan
2013-07-23  2:29         ` Li Zefan
2013-07-23  2:40 ` Myklebust, Trond
2013-07-23  2:40   ` Myklebust, Trond
2013-07-23  2:47   ` James Bottomley
2013-07-23  2:47     ` James Bottomley
2013-07-23  2:57     ` Myklebust, Trond
2013-07-23  2:57       ` Myklebust, Trond

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=1373955031.2148.18.camel@dabdike \
    --to=james.bottomley@hansenpartnership.com \
    --cc=greg@kroah.com \
    --cc=ksummit-2013-discuss@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.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 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.