From: Jan Beulich <jbeulich@suse.com>
To: George Dunlap <George.Dunlap@citrix.com>
Cc: "open list:X86" <xen-devel@lists.xenproject.org>
Subject: Re: [ANNOUNCE] Call for agenda items for December 2020 Community Call @ 16:00 UTC
Date: Mon, 30 Nov 2020 11:25:57 +0100 [thread overview]
Message-ID: <6da4cd56-7364-bc6e-24d8-02976dbd637d@suse.com> (raw)
In-Reply-To: <6A1AC739-EB53-4996-A99B-EE68358E70DB@citrix.com>
On 27.11.2020 12:52, George Dunlap wrote:
> The proposed agenda is in https://cryptpad.fr/pad/#/2/pad/edit/OPN55rXaOncupuWuHxtddzWJ/ and you can edit to add items. Alternatively, you can reply to this mail directly.
The "New series / series requiring attention" section is gone. Was
this intentional? If not, I would have wanted to propose that items
from that list which we didn't get to on the previous call be
automatically propagated. According to my observation it is more
likely than not that nothing would have changed in their status.
Hence it may be easier to take one off the list if indeed it has
got unstalled.
> == Dial-in Information ==
> ## Meeting time
> 16:00 - 17:00 UTC
> Further International meeting times: https://www.timeanddate.com/worldclock/meetingdetails.html?year=2020&month=12&day=3&hour=16&min=0&sec=0&p1=1234&p2=37&p3=224&p4=179
>
>
> ## Dial in details
> Web: https://www.gotomeet.me/GeorgeDunlap
>
> You can also dial in using your phone.
> Access Code: 168-682-109
>
> China (Toll Free): 4008 811084
> Germany: +49 692 5736 7317
From last month's meeting:
Germany: +49 721 9881 4161
Jan
next prev parent reply other threads:[~2020-11-30 10:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 11:52 [ANNOUNCE] Call for agenda items for December 2020 Community Call @ 16:00 UTC George Dunlap
2020-11-30 10:25 ` Jan Beulich [this message]
2020-11-30 12:16 ` George Dunlap
2020-12-03 14:32 ` Jan Beulich
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=6da4cd56-7364-bc6e-24d8-02976dbd637d@suse.com \
--to=jbeulich@suse.com \
--cc=George.Dunlap@citrix.com \
--cc=xen-devel@lists.xenproject.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 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).