public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: daniel.wagner@siemens.com (Daniel Wagner)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] How to develop on the RT version
Date: Thu, 22 Feb 2018 15:58:32 +0100	[thread overview]
Message-ID: <4d0bdf7a-81db-ee4b-4846-cfdde236b201@siemens.com> (raw)
In-Reply-To: <SG2PR06MB11654A3FF485063C01FFC5C58ACD0@SG2PR06MB1165.apcprd06.prod.outlook.com>

Hi Chris,

On 22.02.2018 03:36, Chris Brandt wrote:
> On Wednesday, February 21, 2018, Daniel Sangorrin wrote:
>> The rebase branch is something complimentary, the maintainer may decide
>> not to prepare it (the same with the patches).
>> # The rebase branch might useful to see clearly which patches come from
>> the cip kernel and which ones are from PREEMPT RT.
> 
> OK, that was the info that I needed.

Sorry for the late response.

In short: linux-4.4.y-cip-rt wont be rebased. linux-4.4.y-cip-rt-rebase
tree contains the extracted patches from linux-4.4.y.cip-rt. Some people
like to get a patchset which they can apply on top of some tree. But it
looks no one here around is particular interested in this.

The linux-4.4.y-cip-patches is just a variation from the rebase branch.
Probably not really useful to anyone. I just archived all the a patches
in that branch. It was useful for me when I started with the scripting
to have a backup but I don't think I need it anymore. So if no one needs
I can drop it completely to avoid further confusion.

Thanks,
Daniel

  reply	other threads:[~2018-02-22 14:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-09 14:37 [cip-dev] How to develop on the RT version Chris Brandt
2018-02-22  2:19 ` Daniel Sangorrin
2018-02-22  2:36   ` Chris Brandt
2018-02-22 14:58     ` Daniel Wagner [this message]
2018-02-22 15:41       ` Chris Brandt
2018-02-22  2:22 ` Daniel Sangorrin

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=4d0bdf7a-81db-ee4b-4846-cfdde236b201@siemens.com \
    --to=daniel.wagner@siemens.com \
    --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