Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753618AbcLHPcZ (ORCPT ); Thu, 8 Dec 2016 10:32:25 -0500 Received: from bedivere.hansenpartnership.com ([66.63.167.143]:48488 "EHLO bedivere.hansenpartnership.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752937AbcLHPcU (ORCPT ); Thu, 8 Dec 2016 10:32:20 -0500 Message-ID: <1481211043.2361.1.camel@HansenPartnership.com> Subject: Re: LSF/MM 2017: Call for Proposals From: James Bottomley To: Michal Hocko Cc: Jeff Layton , linux-block@vger.kernel.org, linux-btrfs@vger.kernel.org, linux-cifs@vger.kernel.org, linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-nfs@vger.kernel.org, linux-scsi@vger.kernel.org, "xfs@oss.sgi.com" , ceph-devel@vger.kernel.org, linux-nvme@lists.infradead.org, "lsf-pc@lists.linux-foundation.org" Date: Thu, 08 Dec 2016 07:30:43 -0800 In-Reply-To: <20161208122619.GA26535@dhcp22.suse.cz> References: <1480601506.2511.7.camel@poochiereds.net> <1481122626.2354.14.camel@HansenPartnership.com> <20161208122619.GA26535@dhcp22.suse.cz> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.16.5 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 851 Lines: 23 On Thu, 2016-12-08 at 13:26 +0100, Michal Hocko wrote: > On Wed 07-12-16 06:57:06, James Bottomley wrote: > [...] > > Just on this point, since there seems to be a lot of confusion: lsf > > -pc > > is the list for contacting the programme committee, so you cannot > > subscribe to it. > > > > There is no -discuss equivalent, like kernel summit has, because we > > expect you to cc the relevant existing mailing list and have the > > discussion there instead rather than expecting people to subscribe > > to a > > new list. > > There used to be lsf@lists.linux-foundation.org. Is it not active > anymore? Not until we get the list of invitees sorted out. And then it's only for stuff actually to do with lsf (like logistics, bof or session requests or other meetups). Any technical stuff should still be cc'd to the relevant mailing list. James