From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: ltp@lists.linux.it
Cc: Cyril Hrubis <notifications@github.com>
Subject: Re: [LTP] After release meeting
Date: Wed, 11 Mar 2026 12:41:37 +0000 [thread overview]
Message-ID: <69b16303.050a0220.27d4f3.6151@mx.google.com> (raw)
In-Reply-To: <abFW8JI1H_m1NqS2@redhat.com>
> On Wed, Mar 11, 2026 at 07:38:27PM +0800, Li Wang wrote:
> > On Wed, Mar 11, 2026 at 10:53:07AM +0000, Andrea Cervesato wrote:
> > > Hi!
> > >
> > > > Hello everyone,
> > > >
> > > > what about scheduling a new LTP meeting after the release?
> > > > When's your first available date?
> > > >
> > > > Kind regards,
> > > > --
> > > > Andrea Cervesato
> > > > SUSE QE Automation Engineer Linux
> > > > andrea.cervesato@suse.com
> > >
> > > We still didn't decide a date for the LTP meeting. I was waiting for
> > > more feedbacks.
> > >
> > > @Li WDYT?
> >
> > As long as it's my daytime, any date is fine with me. Thanks!
> > (FYI: 9:00 UTC is 5pm Beijing time).
>
> I just see Cyril prefer 10:00 and 14:00 CET, that unavalibe to me on Wed/Thur.
> But if avoid Wednesday and Thursday, the time-slot works for me:).
>
> --
> Regards,
> Li Wang
>
By looking at the previous meetings, we always did it at 9:00 UTC.
What about Tuesday the 17th at 9:00 UTC (10:00 CET and 18:00 Beijing time) ?
@Li Is it too late for you or we can make it?
--
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-03-11 12:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 10:27 [LTP] After release meeting Andrea Cervesato via ltp
2026-02-17 11:28 ` Cyril Hrubis
2026-02-17 12:45 ` Martin Doucha
2026-03-11 10:53 ` Andrea Cervesato via ltp
2026-03-11 11:38 ` Li Wang via ltp
2026-03-11 11:50 ` Li Wang via ltp
2026-03-11 12:41 ` Andrea Cervesato via ltp [this message]
2026-03-11 12:43 ` Andrea Cervesato via ltp
2026-03-11 13:17 ` Li Wang via ltp
2026-03-11 13:51 ` Petr Vorel
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=69b16303.050a0220.27d4f3.6151@mx.google.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
--cc=notifications@github.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 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.