public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <fedora@leemhuis.info>
To: Willy Tarreau <w@1wt.eu>
Cc: linux-kernel@vger.kernel.org, Adrian Bunk <bunk@stusta.de>,
	stable@kernel.org
Subject: Re: no announce mails for "older" stable-releases on linux-kernel-announce (Was: Re: Linux 2.6.20.16)
Date: Thu, 16 Aug 2007 08:42:29 +0200	[thread overview]
Message-ID: <46C3F1D5.9040604@leemhuis.info> (raw)
In-Reply-To: <20070816062908.GA1620@1wt.eu>

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@vger.kernel.org containing
 the line: [...]

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

CU
thl

  reply	other threads:[~2007-08-16  6:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-16  5:43 Linux 2.6.20.16 Willy Tarreau
2007-08-16  5:47 ` Willy Tarreau
2007-08-16  6:12 ` no announce mails for "older" stable-releases on linux-kernel-announce (Was: Re: Linux 2.6.20.16) Thorsten Leemhuis
2007-08-16  6:29   ` Willy Tarreau
2007-08-16  6:42     ` Thorsten Leemhuis [this message]
2007-08-16 17:23       ` [stable] " Greg KH

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=46C3F1D5.9040604@leemhuis.info \
    --to=fedora@leemhuis.info \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    --cc=w@1wt.eu \
    /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