From: jack@suse.cz (Jan Kara)
Subject: [Lsf-pc] LSF/MM 2017: Call for Proposals
Date: Thu, 8 Dec 2016 13:34:55 +0100 [thread overview]
Message-ID: <20161208123455.GC4049@quack2.suse.cz> (raw)
In-Reply-To: <20161208122619.GA26535@dhcp22.suse.cz>
On Thu 08-12-16 13:26:19, 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 at lists.linux-foundation.org. Is it not active
> anymore?
No sure about the current state but usually it gets populated by the
selected attendees each year.
Honza
--
Jan Kara <jack at suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2016-12-08 12:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 14:11 LSF/MM 2017: Call for Proposals Jeff Layton
2016-12-07 14:57 ` James Bottomley
2016-12-08 12:26 ` Michal Hocko
2016-12-08 12:34 ` Jan Kara [this message]
2016-12-08 15:30 ` James Bottomley
2016-12-08 15:37 ` Michal Hocko
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=20161208123455.GC4049@quack2.suse.cz \
--to=jack@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).