linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ralf Ramsauer <ralf@ramses-pyramidenbau.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: Old split quilt queues
Date: Wed, 20 Jan 2016 23:18:03 +0100	[thread overview]
Message-ID: <56A0079B.3000400@ramses-pyramidenbau.de> (raw)
In-Reply-To: <alpine.DEB.2.11.1601202151200.3575@nanos>

Hi Thomas,

On 01/20/2016 09:59 PM, Thomas Gleixner wrote:
> Ralf,
>
> On Mon, 18 Jan 2016, Ralf Ramsauer wrote:
>
>> I'm looking for older RT split quilt queues, especially those for kernel
>> versions 2.6.31 and 2.6.33.
>> Apparently, these are the only two versions without split quilt queues
>> available on the FTP server.
>>
>> Does someone of you know where to get those patch stacks? Or more
>> precisely: are split quilt queues actually existing for those versions?
> I think that was the time where we actually tried to handle the rt patches in
> git and therefor did not release quilt queues. Those git branches are gone
> from git.kernel.org AFAICT, but I should have an archive somewhere. Poke me
> again in a week if I forget to search for it.
Ok, that's what I thought. A working git repo would really be helpful.
>
>> I'm looking for _all_ available split quilt queues for those versions as
>> I'm doing some analysis on the patch stacks.
> Out of curiousity. What kind of analysis are you doing?
>
> Archaeological studies? I wouldn't be suprised, given that you are in the
> pyramid building business.
Well, yes, kind of. I'm doing some archaeological research, digging deep
inside prehistoric PreemptRT and trying to figure out what we can learn
from history.

RT is a pretty huge patch stack which has been around for a couple of
years. I'm trying to find answers to questions like:
 - how did RT evolve over the years?
 - which kind of patches went upstream?
 - how long did a patch live in the RT stack before it went upstream?
 - which kind of patches tend to stay in the patch stack and will
probably not go upstream?

Therefore I'm happy for anything old that's still available out there.
Anything helps.
I will keep you informed.

Thank you
  Ralf
>
> 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


-- 
Ralf Ramsauer
GPG: 0x8F10049B


  reply	other threads:[~2016-01-20 22:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-18 22:44 Old split quilt queues Ralf Ramsauer
2016-01-20 20:59 ` Thomas Gleixner
2016-01-20 22:18   ` Ralf Ramsauer [this message]
2016-01-28 14:29   ` Ralf Ramsauer
2016-01-29 11:12     ` Thomas Gleixner
2016-01-29 11:14       ` Ralf Ramsauer
2016-01-29 18:23       ` Ralf Ramsauer
2016-01-29 19:56         ` Thomas Gleixner
2016-03-07  3:42           ` Paul Gortmaker
2016-03-07 11:15             ` Ralf Ramsauer
2016-03-14  6:31               ` Paul Gortmaker
2016-03-14  9:26                 ` Ralf Ramsauer

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=56A0079B.3000400@ramses-pyramidenbau.de \
    --to=ralf@ramses-pyramidenbau.de \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).