From: Ian Campbell <ian.campbell@citrix.com>
To: xen-devel@lists.xenproject.org
Subject: Re: [CALL-FOR-AGENDA] Monthly Xen.org Technical Call (2016-01-13)
Date: Fri, 8 Jan 2016 16:50:26 +0000 [thread overview]
Message-ID: <1452271826.26438.59.camel@citrix.com> (raw)
In-Reply-To: <E1aGrKI-0005rn-CD@ukmail1.uk.xensource.com>
On Wed, 2016-01-06 at 16:50 +0000, Ian Campbell wrote:
> The next Xen technical call is scheduled for:
> Wed 13 Jan 17:00:00 GMT 2016
> `date -d @1452704400`
>
> However I am away then.
From tonight in fact, so in the absence of any agenda items so far I'm
going to cancel the call now, slightly ahead of the usual schedule.
Ian.
> In the (unlikely) event there is something to
> discuss then we can either schedule another time or I can find a
> standin to actually run the call.
>
> Note that the time can also be changed if the participants interested in
> the proposed topics are in a timezone which makes this slot inconvenient.
>
> See http://lists.xen.org/archives/html/xen-devel/2015-01/msg00414.html
> for more information on the call.
>
> Please let me know (CC-ing the list) any topics which you would like to
> discuss. It might be useful to include:
>
> * References to any relevant/recent mailing list threads;
> * Other people who you think should be involved in the discussion (and
> CC them);
>
> If you would like to attend then please let me know so I can send you the
> dial in details.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-01-08 16:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-06 16:50 [CALL-FOR-AGENDA] Monthly Xen.org Technical Call (2016-01-13) Ian Campbell
2016-01-08 16:50 ` Ian Campbell [this message]
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=1452271826.26438.59.camel@citrix.com \
--to=ian.campbell@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 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.