From: Juan Quintela <quintela@redhat.com>
To: Bernhard Beschow <shentey@gmail.com>
Cc: afaerber@suse.de, ale@rev.ng, anjo@rev.ng, bazulay@redhat.com,
bbauman@redhat.com, chao.p.peng@linux.intel.com,
cjia@nvidia.com, cw@f00f.org, david.edmondson@oracle.com,
dustin.kirkland@canonical.com, eblake@redhat.com,
edgar.iglesias@gmail.com, elena.ufimtseva@oracle.com,
eric.auger@redhat.com, f4bug@amsat.org,
Felipe Franciosi <felipe.franciosi@nutanix.com>,
"iggy@theiggy.com" <iggy@kws1.com>,
Warner Losh <wlosh@bsdimp.com>,
jan.kiszka@web.de, jgg@nvidia.com, jidong.xiao@gmail.com,
jjherne@linux.vnet.ibm.com, joao.m.martins@oracle.com,
konrad.wilk@oracle.com, kvm@vger.kernel.org,
mburton@qti.qualcomm.com, mdean@redhat.com,
mimu@linux.vnet.ibm.com, peter.maydell@linaro.org,
qemu-devel@nongnu.org, richard.henderson@linaro.org,
shameerali.kolothum.thodi@huawei.com, stefanha@gmail.com,
wei.w.wang@intel.com, z.huo@139.com, zwu.kernel@gmail.com
Subject: Re: QEMU developers fortnightly call for agenda for 2023-05-16
Date: Fri, 12 May 2023 14:04:07 +0200 [thread overview]
Message-ID: <87mt293geg.fsf@secure.mitica> (raw)
In-Reply-To: <452B32A5-8C9E-4A61-B14B-C8AB47D0A3ED@gmail.com> (Bernhard Beschow's message of "Fri, 12 May 2023 11:41:33 +0000")
Bernhard Beschow <shentey@gmail.com> wrote:
> Am 12. Mai 2023 07:35:27 UTC schrieb Juan Quintela <quintela@redhat.com>:
>>juan.quintela@gmail.com wrote:
>>> Hi If you are interested in any topic, please let me know. Later, Juan.
>>
>>Hi folks
>>
>>So far what we have in the agenda is:
>>
>>questions from Mark:
>>- Update on single binary?
>>- What’s the status on the “icount” plugin ?
>>- Also I could do with some help on a specific issue on KVM/HVF memory handling
>>
>>From me:
>>- Small update on what is going on with all the migration changes
>>
>>Later, Juan.
>>
>>
>>> QEMU developers fortnightly conference call
>>> Tuesday 2023-05-16 ⋅ 15:00 – 16:00
>>> Central European Time - Madrid
>>>
>>> Location
>>> https://meet.jit.si/kvmcallmeeting
>
> Hi Juan,
>
> Would it be possible to offer a public calendar entry -- perhaps in
> .ics format -- with above information? Which can be conveniently
> subscribed to via a smartphone app? Which gets updated regularly under
> the same link? Which doesn't (needlessly, anyway) require
> authentcation?
This is enough?
https://calendar.google.com/calendar/event?action=TEMPLATE&tmeid=NWR0NWppODdqNXFyYzAwbzYza3RxN2dob3VfMjAyMzA1MTZUMTMwMDAwWiBlZ2VkN2NraTA1bG11MXRuZ3ZrbDN0aGlkc0Bn&tmsrc=eged7cki05lmu1tngvkl3thids%40group.calendar.google.com&scp=ALL
If that is not enough, if you know the knob to convince google calendar
to do it I am all ears.
Later, Juan.
next prev parent reply other threads:[~2023-05-12 12:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <calendar-f9e06ce0-8972-4775-9a3d-7269ec566398@google.com>
2023-05-09 14:25 ` QEMU developers fortnightly call for agenda for 2023-05-16 Mark Burton
2023-05-09 14:35 ` Juan Quintela
2023-05-12 7:35 ` Juan Quintela
2023-05-12 11:41 ` Bernhard Beschow
2023-05-12 12:04 ` Juan Quintela [this message]
2023-05-13 15:30 ` Bernhard Beschow
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=87mt293geg.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=afaerber@suse.de \
--cc=ale@rev.ng \
--cc=anjo@rev.ng \
--cc=bazulay@redhat.com \
--cc=bbauman@redhat.com \
--cc=chao.p.peng@linux.intel.com \
--cc=cjia@nvidia.com \
--cc=cw@f00f.org \
--cc=david.edmondson@oracle.com \
--cc=dustin.kirkland@canonical.com \
--cc=eblake@redhat.com \
--cc=edgar.iglesias@gmail.com \
--cc=elena.ufimtseva@oracle.com \
--cc=eric.auger@redhat.com \
--cc=f4bug@amsat.org \
--cc=felipe.franciosi@nutanix.com \
--cc=iggy@kws1.com \
--cc=jan.kiszka@web.de \
--cc=jgg@nvidia.com \
--cc=jidong.xiao@gmail.com \
--cc=jjherne@linux.vnet.ibm.com \
--cc=joao.m.martins@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=mburton@qti.qualcomm.com \
--cc=mdean@redhat.com \
--cc=mimu@linux.vnet.ibm.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=shentey@gmail.com \
--cc=stefanha@gmail.com \
--cc=wei.w.wang@intel.com \
--cc=wlosh@bsdimp.com \
--cc=z.huo@139.com \
--cc=zwu.kernel@gmail.com \
/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).