[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-rt-users
Subject:    Re: Old split quilt queues
From:       Thomas Gleixner <tglx () linutronix ! de>
Date:       2016-01-29 19:56:29
Message-ID: alpine.DEB.2.11.1601292053330.3886 () nanos
[Download RAW message or body]

On Fri, 29 Jan 2016, Ralf Ramsauer wrote:
> As I expected, inside that repo are a lot of tags for the various -rt
> versions.
> First I thought, RT would make use of rebasing, like:
>   - Rebase onto the next kernel version and drop unnecessary commits
> (e.g. patches that went upstream)
>   - Do some additional changes
>   - Export vA.B.C...vA.B.C-rtX as split quilt queue
> 
> But afaict, (at least on the old rt-history), you made a lot of merges
> from rt/* branches and added tags describing the -rt version. Then you
> went on merging against master in order to keep up with upstream.
> 
> Given that, how do you create a split quilt queue, that applies against
> an upstream tag?
> 
> For example, let's take the first RT Tag of rt-history: v2.6.31-rc6-rt2
> How would you create a split quilt queue, that applies against v2.6.31-rc6?
> 
> (I need to extract all those split quilt queues RT version<->base
> upstream version)

As I said before: That was an experiment whether git is usable as a tool to
manage something complex as rt. It turned out, that it's not. I recreated a
new quilt queue after I abondoned git for rt.

So creating split queues is going to be a very interesting and tedious
detective work.

Thanks,

	tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
[prev in list] [next in list] [prev in thread] [next in thread]