From: bigeasy@linutronix.de (Sebastian Andrzej Siewior)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [ANNOUNCE] Linux 4.4.15-cip15-rt10
Date: Wed, 10 Jan 2018 18:32:32 +0100 [thread overview]
Message-ID: <20180110173232.krwpnlfeijdseinv@linutronix.de> (raw)
In-Reply-To: <D5D6254030DBC644B6EE58B333BFBB1E9D97B5AF@ORSMSX101.amr.corp.intel.com>
On 2018-01-09 21:31:34 [+0000], Hindman, Gavin wrote:
> Sorry for the top-post. Seems like maybe we are causing confusion by regularly announcing CIP releases on rt-users. Wouldn't anyone interested in CIP already be subscribed to that mailing list and getting announcements that way? Maybe it just needs a clearer header, if we think it should stay on rt-users?
I think the announcement was just fine. Now I do know what it does and
what will happen after Greg decides to put 4.4 EOL.
A pointer to [0] as part of the announcement might be help full. In the
end I think it should remain on rt-users since Steven won't continue
doing 4.4 stable. So Daniel's 4.4-RT on top of the CIP tree will be the
only source of a maintained 4.4-RT tree.
[0] wiki.linuxfoundation.org/civilinfrastructureplatform/cipkernelmaintenance
> Maybe a "related projects" section should be created at https://wiki.linuxfoundation.org/realtime/preempt_rt_versions ?
So what do have in mind? Moving v4.4-RT over to the "No longer
maintained PREEMPT_RT versions" section and adding a new one with
"related projects" where we add the 4.4-cip-rt tree?
Daniel: you have the release currently in a git tree within his "user"
namespace and did not upload it to k.o. Do you plan upload it to the
stable-rt tree like Julia does and upload it to the "projects/rt/4.4"
folder on k.o.? If so we might just add a link to the cip wiki next to
4.4 and be done with it.
Other suggestions?
> -gavin
Sebastian
next prev parent reply other threads:[~2018-01-10 17:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 11:56 [cip-dev] [ANNOUNCE] Linux 4.4.15-cip15-rt10 Daniel Wagner
2018-01-02 12:29 ` Daniel Wagner
2018-01-08 9:33 ` Sebastian Andrzej Siewior
2018-01-08 10:13 ` Daniel Wagner
2018-01-08 10:56 ` Sebastian Andrzej Siewior
2018-01-08 11:45 ` Daniel Wagner
2018-01-08 14:06 ` Jan Kiszka
2018-01-08 14:56 ` Agustín Benito Bethencourt
2018-01-09 21:05 ` Ben Hutchings
2018-01-09 21:31 ` Hindman, Gavin
2018-01-10 17:32 ` Sebastian Andrzej Siewior [this message]
2018-01-11 8:07 ` Daniel Wagner
2018-01-11 16:51 ` Ben Hutchings
2018-01-17 9:18 ` Daniel Wagner
2018-01-10 9:04 ` Daniel Wagner
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=20180110173232.krwpnlfeijdseinv@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=cip-dev@lists.cip-project.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