All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Garrett, Mike (HPE Server Firmware)" <mike.garrett@hpe.com>
To: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: 2.9 planning/progress docs?
Date: Mon, 27 Jul 2020 15:03:21 +0000	[thread overview]
Message-ID: <AT5PR8401MB06263771D26D0EE53D41A5818F720@AT5PR8401MB0626.NAMPRD84.PROD.OUTLOOK.COM> (raw)

[-- Attachment #1: Type: text/plain, Size: 738 bytes --]

Hello,

Is there a good place to find the 2.9 change list, both in progress and planned?  For instance, I noticed a lot of change occurring in the dbus-sensors repo, but I'd like to see what master plan is guiding these commits and when they are "done" for 2.9.  I know things might be more fluid than that, but if there is a doc, I'd like to keep an eye on it.

We have some patches for dbus-sensors specific to our platforms that are frequently being invalidated by updates upstream, and instead of constantly regenerating our patches, it would be nice to know when the upstream has accomplished its goals for 2.9 and we can regenerate our patches once.  We are still getting acquainted with the processes here.

Thanks,

Mike

[-- Attachment #2: Type: text/html, Size: 2751 bytes --]

             reply	other threads:[~2020-07-27 15:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-27 15:03 Garrett, Mike (HPE Server Firmware) [this message]
2020-07-27 15:52 ` 2.9 planning/progress docs? Ed Tanous
2020-10-30  5:15   ` Andrew Jeffery
2020-11-02 22:37     ` Patrick Williams
2020-11-03 12:54       ` Garrett, Mike (HPE Server Firmware)

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=AT5PR8401MB06263771D26D0EE53D41A5818F720@AT5PR8401MB0626.NAMPRD84.PROD.OUTLOOK.COM \
    --to=mike.garrett@hpe.com \
    --cc=openbmc@lists.ozlabs.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.