2.6.13-rc3-mm3 question

2.6.13-rc3-mm3 question

[Radoslaw AstralStorm Szkodzinski]

[-- Attachment #1: Type: text/plain, Size: 547 bytes --]

I wonder which git version is linus.patch updating to, as it certainly isn't
the mostly new git/hg tree (sans ALSA tree merge), as one patch didn't apply cleanly.
(sched-consider-migration-thread-with-smp-nice.patch)
It could be written as a comment, if that's not too hard to do.

What about releasing a secret release just right before -mm in order to avoid
problems like that MTRR problem?
-- 
AstralStorm

GPG Key ID = 0xD1F10BA2
GPG Key fingerprint = 96E2 304A B9C4 949A 10A0  9105 9543 0453 D1F1 0BA2
Please encrypt if you can.

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

Re: 2.6.13-rc3-mm3 question

[Andrew Morton]

Radoslaw "AstralStorm" Szkodzinski <astralstorm@gorzow.mm.pl> wrote:
>
> I wonder which git version is linus.patch updating to, as it certainly isn't
> the mostly new git/hg tree (sans ALSA tree merge), as one patch didn't apply cleanly.

It's there in the patch?

bix:/usr/src/25> head patches/linus.patch 
GIT 41c018b7ecb60b1c2c4d5dee0cd37d32a94c45af master.kernel.org:/pub/scm/linux/kernel/git/torvalds/linux-2.6.git

> (sched-consider-migration-thread-with-smp-nice.patch)
> It could be written as a comment, if that's not too hard to do.
> 
> What about releasing a secret release just right before -mm in order to avoid
> problems like that MTRR problem?

There are always glitches, I'm afraid.

Re: 2.6.13-rc3-mm3 question

[Radoslaw AstralStorm Szkodzinski]

[-- Attachment #1: Type: text/plain, Size: 396 bytes --]

On Thu, 28 Jul 2005 10:55:51 -0700
Andrew Morton <akpm@osdl.org> wrote:

> It's there in the patch?

Well, I didn't check there. Poor stupid me.

> There are always glitches, I'm afraid.

But there could be less build breakers at least.

-- 
AstralStorm

GPG Key ID = 0xD1F10BA2
GPG Key fingerprint = 96E2 304A B9C4 949A 10A0  9105 9543 0453 D1F1 0BA2
Please encrypt if you can.

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

Re: 2.6.13-rc3-mm3 question

[Adrian Bunk]

On Thu, Jul 28, 2005 at 08:31:33PM +0200, Radoslaw AstralStorm Szkodzinski wrote:
> On Thu, 28 Jul 2005 10:55:51 -0700
> Andrew Morton <akpm@osdl.org> wrote:
>...
> > There are always glitches, I'm afraid.
> 
> But there could be less build breakers at least.

The -mm kernels are the result of mixing the latest developments from a 
dozen subsystem trees with a few hundred random patches from 
linux-kernel resulting in the most unstable kernel available. [1]

I'm surprised that you are that much concerned about compile errors when 
using a kernel that might regularly exchange the contents of /dev/hda 
and /dev/null .

cu
Adrian

[1] that's a bit exaggerated and not meant against Andrew

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Re: 2.6.13-rc3-mm3 question

[Radoslaw AstralStorm Szkodzinski]

[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]

On Thu, 28 Jul 2005 22:42:38 +0200
Adrian Bunk <bunk@stusta.de> wrote:


> I'm surprised that you are that much concerned about compile errors when 
> using a kernel that might regularly exchange the contents of /dev/hda 
> and /dev/null .
> 
These bugs don't happen too often in reality.
Just please don't be malicious and add this kind of code deliberately. :)

Every build breaker wastes my precious time to fix it. 
That's compulsive/obsessive in some way. ;)

On the contrary, my "just break it" desktop is destined to have
it's HDD contents overwritten once in a time.
That's what these spare disks/computers are for, aren't they?
All the data on that computer is volatile, all (not too frequent) backup is
mostly made through the network and checked from the stable computer.

If I really needed it very stable, I wouldn't test Reiser4 on it, less so
a development kernel. That's why my stable machine uses latest release kernel,
and only after it's broken in by at least a week.

-- 
AstralStorm

GPG Key ID = 0xD1F10BA2
GPG Key fingerprint = 96E2 304A B9C4 949A 10A0  9105 9543 0453 D1F1 0BA2
Please encrypt if you can.

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

Re: 2.6.13-rc3-mm3 question

[Matthias Urlichs]

Hi, Radoslaw "AstralStorm" Szkodzinski wrote:

> I wonder which git version is linus.patch updating to

Note, if you want -mm as a nice shiny parent-linked git tree, just pull
from http://www.kernel.org/pub/scm/linux/kernel/git/smurf/linux-trees.git
(the whichever-mm-release-you-want branch).

I can import other patchsets that way; just ping me.

-- 
Matthias Urlichs   |   {M:U} IT Design @ m-u-it.de   |  smurf@smurf.noris.de
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
 - -
Nature is the chart of God, mapping out all His attributes; art is the
shadow of His wisdom, and copieth His resources.
					-- Tupper

Re: 2.6.13-rc3-mm3 question

[Adrian Bunk]

On Fri, Jul 29, 2005 at 02:50:34AM +0200, Radoslaw AstralStorm Szkodzinski wrote:
> On Thu, 28 Jul 2005 22:42:38 +0200
> Adrian Bunk <bunk@stusta.de> wrote:
> 
> 
> > I'm surprised that you are that much concerned about compile errors when 
> > using a kernel that might regularly exchange the contents of /dev/hda 
> > and /dev/null .
> > 
> These bugs don't happen too often in reality.
> Just please don't be malicious and add this kind of code deliberately. :)
> 
> Every build breaker wastes my precious time to fix it. 
> That's compulsive/obsessive in some way. ;)
>...

Someone has to test it.

Andrew already wastes some of his precious time for testing before 
releasing a -mm kernel, but this doesn't catch every compile error.

If a -mm kernel doesn't compile for you, you can:
- apply a patch if it is already available
- fix it yourself
- wait for the next -mm

One of the purposes of -mm kernels is actually to find compile errors.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Re: 2.6.13-rc3-mm3 question

[Chuck Ebbert]

Adrian Bunk <bunk@stusta.de> wrote:

> If a -mm kernel doesn't compile for you, you can:
> - apply a patch if it is already available

 But the only place I see to get patches is from the mailing list.
A 'hotfixes' directory for the -mm patches on kernel.org would be nice.




__
Chuck