From: "J.H." <warthog19@eaglescrag.net>
To: Borislav Petkov <bp@alien8.de>, Shea Levy <shea@shealevy.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
ftpadmin@kernel.org
Subject: Re: Release Announcements
Date: Mon, 23 Jul 2012 11:52:42 -0600 [thread overview]
Message-ID: <500D8F6A.2090703@eaglescrag.net> (raw)
In-Reply-To: <20120723082238.GB21615@liondog.tnic>
On 07/23/2012 02:22 AM, Borislav Petkov wrote:
> On Sun, Jul 22, 2012 at 12:08:34PM -0400, Shea Levy wrote:
>> The linux-kernel-announce doesn't seem to have had any traffic
>> since 3.1-rc4 (maybe due to the kernel.org break-in?). Is there a
>> recommended way to get email news of kernel releases without being
>> subscribed to the main kernel list?
>
> Let's CC some more people about this.
>
Follow the respective gitweb RSS feeds? I'll have to do some digging to
figure out where those e-mails got generated from. I do want to say
that that *SHOULD* be working, but if the e-mails aren't showing up in
the archives that may have gotten broken somewhere.
- John 'Warthog9' Hawley
next prev parent reply other threads:[~2012-07-23 17:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-22 16:08 Shea Levy
2012-07-23 8:22 ` Borislav Petkov
2012-07-23 17:52 ` J.H. [this message]
2012-07-24 0:37 ` Shea Levy
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=500D8F6A.2090703@eaglescrag.net \
--to=warthog19@eaglescrag.net \
--cc=bp@alien8.de \
--cc=ftpadmin@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shea@shealevy.com \
/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
Powered by JetHome