From: Willy Tarreau <w@1wt.eu>
To: Thorsten Leemhuis <fedora@leemhuis.info>
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:29:08 +0200 [thread overview]
Message-ID: <20070816062908.GA1620@1wt.eu> (raw)
In-Reply-To: <46C3EAB7.2000503@leemhuis.info>
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.
> If the latter: are those scripts available somewhere?
we all have somewhat different scripts. Those scripts do 80% of the work
depending on our environments, mostly in order to avoid common mistakes,
and we do the remaining 20% by hand. Anyway I think it's not difficult
for any of us to add a new address.
(CCing -stable and Adrian in case they miss your mail)
Regards,
willy
next prev parent reply other threads:[~2007-08-16 6:32 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 [this message]
2007-08-16 6:42 ` Thorsten Leemhuis
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=20070816062908.GA1620@1wt.eu \
--to=w@1wt.eu \
--cc=bunk@stusta.de \
--cc=fedora@leemhuis.info \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
/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