From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Subject: [Ksummit-discuss] Stable and delay backports
Date: Tue, 03 Nov 2015 09:02:35 -0800 [thread overview]
Message-ID: <1446570155.6440.12.camel@HansenPartnership.com> (raw)
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?
James
next reply other threads:[~2015-11-03 17:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 17:02 James Bottomley [this message]
2015-11-03 17:08 ` [Ksummit-discuss] Stable and delay backports Jens Axboe
2015-11-03 18:09 ` James Bottomley
2015-11-03 17:30 ` Greg Kroah-Hartman
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=1446570155.6440.12.camel@HansenPartnership.com \
--to=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 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.