* Chuck Ebbert ([EMAIL PROTECTED]) wrote:
> It is the stable-queue tree that's not up-to-date:
Ah, yes that is updated (but only within the last half-hour or so).
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo
* Chuck Ebbert ([EMAIL PROTECTED]) wrote:
> That tree is not up-to-date. So much for using it to track -stable --
> what should I use instead?
It's updated, perhaps you hit a stale mirror?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
Chuck Ebbert wrote:
> Chris Wright wrote:
>> We (the -stable team) are announcing the release of the 2.6.20.6 kernel.
>> This has 2 important fixes that should have been in 2.6.20.5. They are
>> issues that were pointed with 2.6.20.5 patches during its review cycle,
>> but the patch updates were
Chris Wright wrote:
> We (the -stable team) are announcing the release of the 2.6.20.6 kernel.
> This has 2 important fixes that should have been in 2.6.20.5. They are
> issues that were pointed with 2.6.20.5 patches during its review cycle,
> but the patch updates were mistakenly dropped.
Chris Wright wrote:
We (the -stable team) are announcing the release of the 2.6.20.6 kernel.
This has 2 important fixes that should have been in 2.6.20.5. They are
issues that were pointed with 2.6.20.5 patches during its review cycle,
but the patch updates were mistakenly dropped. Please
Chuck Ebbert wrote:
Chris Wright wrote:
We (the -stable team) are announcing the release of the 2.6.20.6 kernel.
This has 2 important fixes that should have been in 2.6.20.5. They are
issues that were pointed with 2.6.20.5 patches during its review cycle,
but the patch updates were
* Chuck Ebbert ([EMAIL PROTECTED]) wrote:
That tree is not up-to-date. So much for using it to track -stable --
what should I use instead?
It's updated, perhaps you hit a stale mirror?
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
* Chuck Ebbert ([EMAIL PROTECTED]) wrote:
It is the stable-queue tree that's not up-to-date:
Ah, yes that is updated (but only within the last half-hour or so).
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo
diff --git a/Makefile b/Makefile
index 3f194d1..e81e106 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 20
-EXTRAVERSION = .5
+EXTRAVERSION = .6
NAME = Homicidal Dwarf Hamster
# *DOCUMENTATION*
diff --git a/crypto/scatterwalk.c
v2.6.20.5 to v2.6.20.6
==
Chris Wright (1):
Linux 2.6.20.6
Herbert Xu (1):
CRYPTO api: Use the right value when advancing scatterwalk_copychunks
Paolo 'Blaisorblade' Giarrusso (1):
uml: fix static linking for real
-
To unsubscribe from
v2.6.20.5 to v2.6.20.6
==
Chris Wright (1):
Linux 2.6.20.6
Herbert Xu (1):
CRYPTO api: Use the right value when advancing scatterwalk_copychunks
Paolo 'Blaisorblade' Giarrusso (1):
uml: fix static linking for real
-
To unsubscribe from
diff --git a/Makefile b/Makefile
index 3f194d1..e81e106 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 20
-EXTRAVERSION = .5
+EXTRAVERSION = .6
NAME = Homicidal Dwarf Hamster
# *DOCUMENTATION*
diff --git a/crypto/scatterwalk.c
12 matches
Mail list logo
