From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Marcus Hoffmann <buildroot@bubu1.eu>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/systemd: bump to version 254.9
Date: Wed, 21 Feb 2024 18:08:14 +0100 [thread overview]
Message-ID: <ZdYt_stfXR6pbvR5@landeda> (raw)
In-Reply-To: <04a28a98-2699-44b6-b5d5-697a1a6fe893@bubu1.eu>
Marcus, All,
+Thomas
On 2024-02-19 22:30 +0100, Marcus Hoffmann via buildroot spake thusly:
> On 19.02.24 22:14, Yann E. MORIN wrote:
> > Please watch the gitlab pipeline for any failure of the runtimet tests,
> > just in case this minor version bump breaks anything.
> So if I understood that correctly I can add myself as a maintainer of the
> runtime test files and I'll get an email when that test fails? Or is that
> not how it works?
As far as I understand, yes, this is what should happen. Thomas has some
scripting (somewhere!) that sends the daily emails, so he'd have the
authoritative answer.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-02-21 17:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 18:26 [Buildroot] [PATCH] package/systemd: bump to version 254.9 Marcus Hoffmann via buildroot
2024-02-19 21:14 ` Yann E. MORIN
2024-02-19 21:30 ` Marcus Hoffmann via buildroot
2024-02-21 17:08 ` Yann E. MORIN [this message]
2024-02-21 17:45 ` Thomas Petazzoni via buildroot
2024-03-16 21:27 ` Peter Korsgaard
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=ZdYt_stfXR6pbvR5@landeda \
--to=yann.morin.1998@free.fr \
--cc=buildroot@bubu1.eu \
--cc=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.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