ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <greg@kroah.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] Stable and delay backports
Date: Tue, 3 Nov 2015 09:30:12 -0800	[thread overview]
Message-ID: <20151103173012.GA31651@kroah.com> (raw)
In-Reply-To: <1446570155.6440.12.camel@HansenPartnership.com>

On Tue, Nov 03, 2015 at 09:02:35AM -0800, James Bottomley wrote:
> I'm still not clear, even after all the discussion, whether there's any
> value left to annotating the cc to stable with a delay backport.  I'm
> getting ready to post a fix to our block size calculations which make
> them completely accurate instead of within 5% like they were before.
> Technically this is a bug fix because people get distressed even over
> apparently losing 5% of their space, so it will have to be backported,
> but the algorithm has increased in complexity, so it would be better to
> incubate in main line for a while to make sure there are no further
> complaints.
> 
> So the question: I think I heard Greg say you're automatically delaying
> merge window backports anyway, so there's no real need to add a separate
> delay tag, or is there?

If you want to ensure that I don't instantly pick it up, sure, put a
"add to stable after XXX" marking on the patch, or do like Jens
suggested, either will work.

thanks,

greg k-h

      parent reply	other threads:[~2015-11-03 17:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-03 17:02 James Bottomley
2015-11-03 17:08 ` Jens Axboe
2015-11-03 18:09   ` James Bottomley
2015-11-03 17:30 ` Greg Kroah-Hartman [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=20151103173012.GA31651@kroah.com \
    --to=greg@kroah.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --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