From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: Bernd Kuhls <bernd@kuhls.net>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/ntp: fix build with GCC 14.x
Date: Sat, 18 May 2024 12:16:03 +0200 [thread overview]
Message-ID: <Zkh_4z6uQm4QNOds@landeda> (raw)
In-Reply-To: <CAGm1_kuhYZ1uCnWquBBnhS89T7antGULc811jzaMAhtiHKFJJg@mail.gmail.com>
Yegor, All,
On 2024-05-18 12:00 +0200, Yegor Yefremov spake thusly:
> Now, it is official: https://bugs.ntp.org/show_bug.cgi?id=3926
That's great, thanks! And upstream looks quite happy with it. :-)
> I'll wait till the patch is committed and then will make v2.
You don't need to wait for the patch to be applied upstream; just add an
upstream tag to the patch, pointing to that bug report:
Upstream: https://bugs.ntp.org/show_bug.cgi?id=3926
Signed-off-by: You
That way, the next person to bump ntp can assess whether that patch
needs to be carried/rebased/dropped, by checking the upstream status.
Thanks!
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-05-18 10:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 12:00 [Buildroot] [PATCH] package/ntp: fix build with GCC 14.x yegorslists--- via buildroot
2024-05-17 18:25 ` Yann E. MORIN
2024-05-18 10:00 ` Yegor Yefremov via buildroot
2024-05-18 10:16 ` Yann E. MORIN [this message]
2024-05-21 9:35 ` Yegor Yefremov via buildroot
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=Zkh_4z6uQm4QNOds@landeda \
--to=yann.morin.1998@free.fr \
--cc=bernd@kuhls.net \
--cc=buildroot@buildroot.org \
--cc=yegorslists@googlemail.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