Re: no announce mails for "older" stable-releases on linux-kernel-announce(Was: Re: Linux 2.6.20.16)

[Thorsten Leemhuis]

On 16.08.2007 08:29, Willy Tarreau wrote:
> On Thu, Aug 16, 2007 at 08:12:07AM +0200, Thorsten Leemhuis wrote:
>> On 16.08.2007 07:43, Willy Tarreau wrote:
>>> I've just released Linux 2.6.20.16. This version catches up with 2.6.21.7.
>>> I hope to issue newer releases soon with next batches of pending patches.
>>>
>>> I'll also be replying to this message with a copy of the patch between
>>> 2.6.20.15 and 2.6.20.16.
>>> [...]
>> Just wondering -- Kernels like this (or 2.6.16.x, 2.6.21.x as well as
>> 2.6.22.x once 2.6.23 got released) don't get announced on
>> linux-kernel-announce. Is that on purpose or a misbehavior of scripts
>> that create the messages for linux-kernel-announce?
> even simpler : I've never been aware of linux-kernel-announce. It's
> possible that only Linus sends there and that even the -stable team
> does not use/know about it either.

Mails for the current stable-releases get out there -- e.g. I received a
"Linux kernel 2.6.22.3 released" not that long ago (that particular one
was broken, but that's another story mentioned somewhere else on LKML
already).

If just seems that 2.6.21.x (or 2.6.20.x or 2.6.16.x) don't get
mentioned on the list because some script likely does a check like this:

if 2.6.22.3 > 2.6.20.16;
then
	# don't send mail
	exit
fi

>> > If the latter: are those scripts available somewhere?
> we all have somewhat different scripts. [...]

I tend to think it's a script that runs on a server site somewhere to
generates those mails, as they contain the text:

 This is an automatically generated message.  To unsubscribe from this
 list, please send a message to majordomo@xxxxxxxxxxxxxxx containing
 the line: [...]

But maybe I'm wrong with that assumption...

CU
thl
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/