From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v5 0/4] Support for Patchwork CI
Date: Fri, 11 Apr 2025 14:10:25 +0200 [thread overview]
Message-ID: <Z_kGsUpRRGBwhEI0@yuki.lan> (raw)
In-Reply-To: <20250411120714.GA319294@pevik>
Hi!
> Andrea did a great effort. Unfortunately we deal with problem probably caused by
> our mailing list because 3rd commit "ci: add ci-patchwork-trigger workflow" did
> not arrive to mailing list.
>
> I suppose the branch is visible on Andrea's fork:
>
> https://github.com/acerv/ltp/tree/refs/heads/b4/patchwork_ci
>
> Mail is not in "ending moderator requests" on https://lists.linux.it/,
> I guess we need to contact ML administrators, I'll do it and Cc you.
Wait a bit I'm helping Andrea to debug his email setup.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-04-11 12:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 11:43 [LTP] [PATCH v5 0/4] Support for Patchwork CI Andrea Cervesato
2025-04-11 11:43 ` [LTP] [PATCH v5 1/4] ci: install dependences for patchwork-ci script Andrea Cervesato
2025-04-14 12:51 ` Petr Vorel
2025-04-14 13:00 ` Andrea Cervesato via ltp
2025-04-11 11:43 ` [LTP] [PATCH v5 2/4] ci: add patchwork communication script Andrea Cervesato
2025-04-14 14:02 ` Petr Vorel
2025-04-15 8:50 ` Andrea Cervesato via ltp
2025-04-15 9:04 ` Petr Vorel
2025-04-11 11:43 ` [LTP] [PATCH v5 4/4] ci: apply patchwork series in ci-docker-build workflow Andrea Cervesato
2025-04-11 12:07 ` [LTP] [PATCH v5 0/4] Support for Patchwork CI Petr Vorel
2025-04-11 12:10 ` Cyril Hrubis [this message]
2025-04-11 12:59 ` Petr Vorel
2025-04-11 13:06 ` Andrea Cervesato via ltp
2025-04-14 15:41 ` Petr Vorel
2025-04-15 7:53 ` Andrea Cervesato via ltp
2025-04-15 9:49 ` Petr Vorel
2025-04-15 9:54 ` Andrea Cervesato via ltp
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=Z_kGsUpRRGBwhEI0@yuki.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
/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.