From: Juan Quintela <quintela@redhat.com>
To: Mark Burton <mark.burton@greensocs.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Damien Hedde" <damien.hedde@greensocs.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Markus Armbruster" <armbru@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Mirela Grujic" <mirela.grujic@greensocs.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>
Subject: Re: "Startup" meeting (was Re: Meeting today?)
Date: Tue, 08 Feb 2022 13:35:49 +0100 [thread overview]
Message-ID: <87k0e57cyi.fsf@secure.mitica> (raw)
In-Reply-To: <38067656-7C95-4CA2-8860-1E5E37CDCDA9@greensocs.com> (Mark Burton's message of "Tue, 8 Feb 2022 12:52:08 +0100")
Mark Burton <mark.burton@greensocs.com> wrote:
> Hi Juan, is there a meeting today? I think the plan was to talk about ’startup’ itself ?
> Cheers
> Mark.
Hi Mark
Yeap. I asked for it on last meeting. The call for topics is on the
list (not that anyone else has answered)
Later, Juan.
>
>> On 25 Jan 2022, at 11:58, Juan Quintela <quintela@redhat.com> wrote:
>>
>> Philippe Mathieu-Daudé <f4bug@amsat.org> wrote:
>>> On 1/25/22 09:50, Juan Quintela wrote:
>>>> Mark Burton <mark.burton@greensocs.com> wrote:
>>>>> All, I believe we will have a followup meeting this coming Tuesday
>>>>> 25th January, at 15:00 (presumably using the same link:
>>>>> https://redhat.bluejeans.com/5402697718).
>>>>>
>>>>> We (GreenSocs/Xilinx) would like to quickly show what now ‘works’, and to give an update on the patches.
>>>>
>>>> I send the call for agenda already.
>>>>
>>>> We are having the meeting.
>>>
>>> Do we need to stick to bluejeans, or can we switch to something more
>>> generic to easily record the call, and be able to start when Juan is
>>> not available?
>>
>> Hi
>>
>> Anyone from inside Red Hat can start the call. So I think that starting
>> the call shouldn't be a problem.
>>
>> If I remember correctly, one of the reasons for using bluejeans was that
>> in the past we used to be around 40 people on the call, and that was not
>> easy to setup. Perhaps today it is different.
>>
>> About recording, I will ask everybody if they agree on the call and we
>> can record it. On the past we _didn't_ want recordings, but I can't
>> remember the reason.
>>
>> Later, Juan.
>>
next prev parent reply other threads:[~2022-02-08 13:58 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 6:57 Redesign of QEMU startup & initial configuration Markus Armbruster
2021-12-09 19:11 ` Daniel P. Berrangé
2021-12-09 20:01 ` Mark Burton
2021-12-09 20:28 ` Daniel P. Berrangé
2021-12-10 8:34 ` Paolo Bonzini
2021-12-10 11:25 ` Daniel P. Berrangé
2021-12-10 14:15 ` Mark Burton
2021-12-10 14:26 ` Daniel P. Berrangé
2021-12-10 14:42 ` Mark Burton
2021-12-10 15:13 ` Paolo Bonzini
2021-12-10 15:26 ` Markus Armbruster
2021-12-10 15:39 ` Daniel P. Berrangé
2021-12-13 15:19 ` Markus Armbruster
2021-12-13 17:30 ` Paolo Bonzini
2021-12-13 17:59 ` Daniel P. Berrangé
2021-12-13 20:22 ` Mark Burton
2021-12-14 13:05 ` Daniel P. Berrangé
2021-12-14 13:11 ` Mark Burton
2021-12-14 13:21 ` Daniel P. Berrangé
2021-12-14 13:36 ` Mark Burton
2021-12-14 13:48 ` Daniel P. Berrangé
2021-12-14 14:42 ` Mark Burton
2021-12-14 14:56 ` Daniel P. Berrangé
2021-12-14 15:12 ` Markus Armbruster
2021-12-14 15:14 ` Mark Burton
2021-12-10 13:54 ` Markus Armbruster
2021-12-10 15:38 ` Paolo Bonzini
2021-12-13 15:28 ` Markus Armbruster
2021-12-13 17:37 ` Paolo Bonzini
2021-12-13 18:07 ` Daniel P. Berrangé
2021-12-13 18:37 ` Paolo Bonzini
2021-12-13 18:53 ` Daniel P. Berrangé
2021-12-14 7:09 ` Meeting today? Mark Burton
2021-12-14 11:37 ` Markus Armbruster
2021-12-14 11:39 ` Mark Burton
2021-12-14 12:49 ` Daniel P. Berrangé
2021-12-14 14:49 ` Markus Armbruster
2022-01-04 9:29 ` Edgar E. Iglesias
2022-01-06 11:21 ` "Startup" meeting (was Re: Meeting today?) Mark Burton
2022-01-06 11:23 ` Daniel P. Berrangé
2022-01-11 10:20 ` Philippe Mathieu-Daudé
2022-01-11 10:22 ` Mark Burton
2022-01-17 17:13 ` Kevin Wolf
2022-01-17 19:02 ` Markus Armbruster
2022-01-23 20:49 ` Mark Burton
2022-01-25 8:50 ` Juan Quintela
2022-01-25 10:45 ` Philippe Mathieu-Daudé via
2022-01-25 10:58 ` Juan Quintela
2022-02-08 11:52 ` Mark Burton
2022-02-08 12:35 ` Juan Quintela [this message]
2022-01-11 10:28 ` Daniel P. Berrangé
2021-12-15 18:46 ` Redesign of QEMU startup & initial configuration Paolo Bonzini
2021-12-15 18:50 ` Daniel P. Berrangé
2021-12-14 11:48 ` Markus Armbruster
2021-12-14 13:00 ` Mark Burton
2021-12-14 14:54 ` Markus Armbruster
2021-12-15 20:00 ` Paolo Bonzini
2021-12-15 20:14 ` Mark Burton
2021-12-16 10:24 ` Markus Armbruster
2021-12-16 15:28 ` Paolo Bonzini
2021-12-16 15:40 ` Daniel P. Berrangé
2021-12-16 16:00 ` Mark Burton
2021-12-16 16:15 ` Daniel P. Berrangé
2021-12-16 16:27 ` Mark Burton
2021-12-13 10:51 ` Damien Hedde
2021-12-13 15:47 ` Markus Armbruster
2022-01-04 12:40 ` Richard W.M. Jones
2022-01-13 16:10 ` Markus Armbruster
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=87k0e57cyi.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=damien.hedde@greensocs.com \
--cc=edgar.iglesias@gmail.com \
--cc=f4bug@amsat.org \
--cc=kwolf@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mark.burton@greensocs.com \
--cc=mirela.grujic@greensocs.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@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 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).