From: Stewart Smith <stewart@linux.ibm.com>
To: Joel Stanley <joel@jms.id.au>, Tao Ren <taoren@fb.com>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Linux kenrel: Moving to a 4.17 base
Date: Thu, 31 May 2018 17:58:37 +1000 [thread overview]
Message-ID: <87sh6845oy.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <CACPK8XfTDqprASF==8wjeH+KnpECiJHrSiQ9ugYuBEe+RM4tgw@mail.gmail.com>
Joel Stanley <joel@jms.id.au> writes:
> A non-goal is to maintain a long-lived stable tree, as this takes time
> away from the first goal.
Although syncing an openbmc release with an LTS kernel is probably a
good idea if someone wants a tree that's going to get some kind of
maintenance for a long time?
--
Stewart Smith
OPAL Architect, IBM.
next prev parent reply other threads:[~2018-05-31 7:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 8:48 Linux kenrel: Moving to a 4.17 base Joel Stanley
2018-05-30 19:15 ` Tao Ren
2018-05-31 7:58 ` Stewart Smith [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-29 12:36 Joel Stanley
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=87sh6845oy.fsf@linux.vnet.ibm.com \
--to=stewart@linux.ibm.com \
--cc=joel@jms.id.au \
--cc=openbmc@lists.ozlabs.org \
--cc=taoren@fb.com \
/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.