From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754984Ab2GXAhw (ORCPT ); Mon, 23 Jul 2012 20:37:52 -0400 Received: from caibbdcaaaaf.dreamhost.com ([208.113.200.5]:46688 "EHLO homiemail-a48.g.dreamhost.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752824Ab2GXAhu (ORCPT ); Mon, 23 Jul 2012 20:37:50 -0400 X-Greylist: delayed 116954 seconds by postgrey-1.27 at vger.kernel.org; Mon, 23 Jul 2012 20:37:50 EDT DomainKey-Signature: a=rsa-sha1; c=nofws; d=shealevy.com; h=message-id:date :from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=shealevy.com; b=dkUdSRdn9YYBK8GSdDXFmgWQc7dEiNSoc5dX5cMxGPe1bt6BWp47jV/fN7F3l vIDOUC1tUrx1XZlCLnmPmU0bRDXQG3ODuZYdMfUnciPHr1JBWkNnNJWWECNjM63i bd6XA0owNvOfZNG8W6gEipH8xMYOfQMvj9P/tf2nJnp6Yk= Message-ID: <500DEE5B.9020504@shealevy.com> Date: Mon, 23 Jul 2012 20:37:47 -0400 From: Shea Levy User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120703 Thunderbird/11.0.1 MIME-Version: 1.0 To: "J.H." CC: Borislav Petkov , "linux-kernel@vger.kernel.org" , ftpadmin@kernel.org Subject: Re: Release Announcements References: <1C17E3CE-50F0-4A56-BCCB-201C6E39E980@shealevy.com> <20120723082238.GB21615@liondog.tnic> <500D8F6A.2090703@eaglescrag.net> In-Reply-To: <500D8F6A.2090703@eaglescrag.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 07/23/2012 01:52 PM, J.H. wrote: > 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? Fair enough, I'll do this until another solution is forthcoming. > 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. They're not just not showing up in the archives, I subscribed a week or so before the 3.5 release and I've not gotten a single mail yet. Cheers, Shea