From: Kamal Mostafa <kamal@canonical.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
kernel-team@lists.ubuntu.com, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [3.8.y.z extended stable] Linux 3.8.13.28 stable review
Date: Mon, 25 Aug 2014 12:14:18 -0700 [thread overview]
Message-ID: <1408994058.8997.33.camel@fourier> (raw)
In-Reply-To: <20140825170033.GA18021@kroah.com>
On Mon, 2014-08-25 at 10:00 -0700, Greg KH wrote:
> On Mon, Aug 25, 2014 at 09:54:46AM -0700, Kamal Mostafa wrote:
> > This is the start of the review cycle for the Linux 3.8.13.28 stable kernel.
> >
> > ** NOTE: This will be the last Linux 3.8.y.z extended stable version
> > ** to be released and supported by me and the Ubuntu Kernel team.
>
> I know this is the last release, but I have gotten some complaints by
> people who are confused by the numbering scheme you are using for the
> Canonical stable kernel releases. Can you please use the EXTRAVERSION
> field with a "-something" tag in it to differenciate from the "normal"
> kernel.org stable releases?
We'll consider that idea for future extended stable versions maintained
by our team.
Thanks,
-Kamal
> A simple "-ubuntu" or "-canonical" or "-fuzzy_bunnies" marking would be
> fine, or whatever you want to pick.
>
> Everyone used to do this a long time ago when we had lots of different
> kernel releases / trees floating around in the pre-git days, which made
> things much easier to figure out where the trees came from.
>
> thanks,
>
> greg k-h
>
next prev parent reply other threads:[~2014-08-25 19:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-25 16:54 [3.8.y.z extended stable] Linux 3.8.13.28 stable review Kamal Mostafa
2014-08-25 16:54 ` [PATCH 3.8 01/13] x86_32, entry: Do syscall exit work on badsys (CVE-2014-4508) Kamal Mostafa
2014-08-25 16:54 ` [PATCH 3.8 02/13] x86_32, entry: Store badsys error code in %eax Kamal Mostafa
2014-08-25 16:54 ` [PATCH 3.8 03/13] shmem: fix faulting into a hole while it's punched Kamal Mostafa
2014-08-25 16:54 ` [PATCH 3.8 04/13] shmem: fix faulting into a hole, not taking i_mutex Kamal Mostafa
2014-08-25 16:54 ` [PATCH 3.8 05/13] shmem: fix splicing from a hole while it's punched Kamal Mostafa
2014-08-25 16:54 ` [PATCH 3.8 06/13] target: Explicitly clear ramdisk_mcp backend pages Kamal Mostafa
2014-08-25 16:54 ` [PATCH 3.8 07/13] sctp: Fix sk_ack_backlog wrap-around problem Kamal Mostafa
2014-08-25 16:54 ` [PATCH 3.8 08/13] mnt: Only change user settable mount flags in remount Kamal Mostafa
2014-08-25 16:54 ` [PATCH 3.8 09/13] mnt: Move the test for MNT_LOCK_READONLY from change_mount_flags into do_remount Kamal Mostafa
2014-08-25 16:54 ` [PATCH 3.8 10/13] mnt: Correct permission checks in do_remount Kamal Mostafa
2014-08-25 16:54 ` [PATCH 3.8 11/13] mnt: Change the default remount atime from relatime to the existing value Kamal Mostafa
2014-08-25 16:54 ` [PATCH 3.8 12/13] ptrace,x86: force IRET path after a ptrace_stop() Kamal Mostafa
2014-08-25 16:54 ` [PATCH 3.8 13/13] net/l2tp: don't fall back on UDP [get|set]sockopt Kamal Mostafa
2014-08-25 17:00 ` [3.8.y.z extended stable] Linux 3.8.13.28 stable review Greg KH
2014-08-25 19:14 ` Kamal Mostafa [this message]
2014-08-25 19:37 ` Greg KH
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=1408994058.8997.33.camel@fourier \
--to=kamal@canonical.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=kernel-team@lists.ubuntu.com \
--cc=linux-kernel@vger.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).