Skip to contentSkip to conversation

patch-2.6.21.3-rt9 misnamed?

DISCUSSION K.R. Foley 4 participants 8 messages May 31, 2007 – Jun 4, 2007

lore
Share & tools
lore

K.R. Foley

author
#0 lore raw

Ingo,

I believe that patch-2.6.21.3-rt9 is misnamed. It applies cleanly to 2.6.21 but seems to contain stuff that is already in 2.6.21.3.

Signature · 1 line
   kr
#1 lore raw
Quoted 4 lines · K.R. Foley

Ingo,

I believe that patch-2.6.21.3-rt9 is misnamed. It applies cleanly to 2.6.21 but seems to contain stuff that is already in 2.6.21.3.

yes - it includes all of 2.6.21.3.

Ingo

author
#2 lore raw
Quoted 11 lines · Ingo Molnar
Quoted 4 lines · K.R. Foley

Ingo,

I believe that patch-2.6.21.3-rt9 is misnamed. It applies cleanly to 2.6.21 but seems to contain stuff that is already in 2.6.21.3.

yes - it includes all of 2.6.21.3.

Ingo

So actually it is not really misnamed, it's just done a bit differently than previous versions. Sorry.

Signature · 1 line
   kr
#3 lore raw
Quoted 8 lines · K.R. Foley
Quoted 7 lines · Ingo Molnar
Quoted 4 lines · K.R. Foley

Ingo,

I believe that patch-2.6.21.3-rt9 is misnamed. It applies cleanly to 2.6.21 but seems to contain stuff that is already in 2.6.21.3.

Quoted 7 lines
Quoted 4 lines

yes - it includes all of 2.6.21.3.

Ingo

So actually it is not really misnamed, it's just done a bit differently than previous versions. Sorry.

yeah. Maybe we should make the 2.6.21.3 -rt patches relative to 2.6.21.3
- but that would be one extra patching step for people who already have a 2.6.21 tree. But ... maybe that makes the most sense after all.

Ingo

author
#4 lore raw
Quoted 13 lines · Ingo Molnar
Quoted 11 lines · K.R. Foley
Quoted 10 lines · Ingo Molnar
Quoted 4 lines · K.R. Foley

Ingo,

I believe that patch-2.6.21.3-rt9 is misnamed. It applies cleanly to 2.6.21 but seems to contain stuff that is already in 2.6.21.3.

yes - it includes all of 2.6.21.3.

Ingo

Quoted 9 lines
Quoted 2 lines

So actually it is not really misnamed, it's just done a bit differently than previous versions. Sorry.

yeah. Maybe we should make the 2.6.21.3 -rt patches relative to 2.6.21.3
- but that would be one extra patching step for people who already have a 2.6.21 tree. But ... maybe that makes the most sense after all.

Ingo

Well don't change any of this on my account. Whatever is easiest for everyone else is fine with me. I was merely pointing it out to possibly help someone else out rather than as a complaint.

Signature · 1 line
   kr
#5 lore raw
In reply to Ingo Molnar
Quoted 16 lines · Ingo Molnar
Quoted 13 lines · K.R. Foley
Quoted 11 lines · Ingo Molnar
Quoted 4 lines · K.R. Foley

Ingo,

I believe that patch-2.6.21.3-rt9 is misnamed. It applies cleanly to 2.6.21 but seems to contain stuff that is already in 2.6.21.3.

yes - it includes all of 2.6.21.3.

Ingo

Quoted 6 lines
Quoted 2 lines

So actually it is not really misnamed, it's just done a bit differently than previous versions. Sorry.

yeah. Maybe we should make the 2.6.21.3 -rt patches relative to 2.6.21.3
- but that would be one extra patching step for people who already have a 2.6.21 tree. But ... maybe that makes the most sense after all.

Including 2.6.21.3 in your patch will break ketchup.

Signature · 1 line
Mathematics is the supreme nostalgia of our time.
#6 lore raw
Quoted 13 lines · On Friday 01 June 2007 18:11:11 Matt Mackall wrote:
Quoted 12 lines · Ingo Molnar
Quoted 11 lines · K.R. Foley
Quoted 9 lines · Ingo Molnar
Quoted 4 lines · K.R. Foley

Ingo,

I believe that patch-2.6.21.3-rt9 is misnamed. It applies cleanly to 2.6.21 but seems to contain stuff that is already in 2.6.21.3.

yes - it includes all of 2.6.21.3.

Ingo

Quoted 8 lines
Quoted 6 lines
Quoted 2 lines

So actually it is not really misnamed, it's just done a bit differently than previous versions. Sorry.

yeah. Maybe we should make the 2.6.21.3 -rt patches relative to 2.6.21.3
- but that would be one extra patching step for people who already have a 2.6.21 tree. But ... maybe that makes the most sense after all.

Including 2.6.21.3 in your patch will break ketchup.

ketchup already breaks with the current rt9 patch.

lapdog{rt}$ ketchup -n 2.6-rt
None -> 2.6.21.3-rt9
Unpacking linux-2.6.21.tar.bz2
Applying patch-2.6.21.3.bz2
Applying patch-2.6.21.3-rt9
lapdog{rt}$ head which ketchup
#!/usr/bin/python
#

# ketchup 0.9.8
# http://selenic.com/ketchup/wiki

As noted before rt9 is based one 2.6.21 so after ketchup brings the directory to 2.6.21.3 then applying rt9 fails.

I would appreciate it if you base the rtX patch on the kernel you list as a prefix of that patch. It helps us that use ketchup and it just makes sense.

-Joachim

#7 lore raw
Quoted 3 lines · Joachim Deguara
Quoted 1 line

Including 2.6.21.3 in your patch will break ketchup.

ketchup already breaks with the current rt9 patch.

we'll release -rt10 probably later today, which will fix this. (it will be named 2.6.21.3-rt10 and will be against 2.6.21.3)

Ingo