From: Jan Kara <jack@suse.cz>
To: Paolo Valente <paolo.valente@linaro.org>
Cc: Bart Van Assche <bart.vanassche@sandisk.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"ulf.hansson@linaro.org" <ulf.hansson@linaro.org>,
"lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
"broonie@linaro.org" <broonie@linaro.org>
Subject: Re: [Lsf-pc] [LSF/MM ATTEND AND AGENDA TOPIC] request to attend the summit
Date: Wed, 4 Jan 2017 08:41:31 +0100 [thread overview]
Message-ID: <20170104074131.GG3780@quack2.suse.cz> (raw)
In-Reply-To: <AB3AF3AB-B6BC-47E7-A67D-793411F46B31@linaro.org>
On Tue 03-01-17 18:23:17, Paolo Valente wrote:
>
> > Il giorno 03 gen 2017, alle ore 13:00, Bart Van Assche <bart.vanassche@sandisk.com> ha scritto:
> >
> > On Tue, 2017-01-03 at 10:39 +0100, Paolo Valente wrote:
> >> In this respect, I hope that the committee does not meet too soon.
> >
> > Hello Paolo,
> >
>
> Hi
>
> > I don't know when the program committee will meet. However, what I
> > remember from previous editions of the LSF/MM is that changes of the
> > agenda happened not only during the weeks before the LSF/MM but even
> > during the LSF/MM.
> >
>
> That would be perfectly fine. The only piece of information that I
> would need in advance is whether my request to attend is accepted, so
> that I can organize my travel and really participate.
We certainly notify selected people (and also rejected ones) enough in
advance.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2017-01-04 7:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-02 18:14 [LSF/MM ATTEND AND AGENDA TOPIC] request to attend the summit Paolo Valente
2017-01-03 8:17 ` Bart Van Assche
2017-01-03 9:39 ` Paolo Valente
2017-01-03 12:00 ` Bart Van Assche
2017-01-03 17:23 ` Paolo Valente
2017-01-04 7:41 ` Jan Kara [this message]
2017-01-08 16:30 ` Bart Van Assche
2017-01-08 16:56 ` Paolo Valente
2017-01-10 9:55 ` Ulf Hansson
2017-01-06 23:05 ` Adam Manzanares
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=20170104074131.GG3780@quack2.suse.cz \
--to=jack@suse.cz \
--cc=bart.vanassche@sandisk.com \
--cc=broonie@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-block@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=paolo.valente@linaro.org \
--cc=ulf.hansson@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.