From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Alexis Lothoré" <alexis.lothore@bootlin.com>
Cc: "Romain Naour" <romain.naour@smile.fr>,
buildroot@buildroot.org,
"Hervé Codina" <herve.codina@bootlin.com>,
"Nicolas Carrier" <nicolas.carrier@nav-timing.safrangroup.com>
Subject: Re: [Buildroot] [PATCH v2] package/php-lua: fix build with PHP8/GCC14
Date: Wed, 13 Aug 2025 12:43:53 +0200 [thread overview]
Message-ID: <20250813124353.4015c466@windsurf> (raw)
In-Reply-To: <DBZCJ6MUT01E.IED2BZIAW291@bootlin.com>
On Mon, 11 Aug 2025 07:24:07 +0200
Alexis Lothoré <alexis.lothore@bootlin.com> wrote:
> > Check-package warn about missing "Upstream:" link.
> >
> > Since the patch come from a fork, using "Upstream" looks wrong here.
> > Maybe Upstream: n/a ?
>
> Sure, I can add this empty Upstream in the next revision.
I don't think "Upstream: n/a" is very useful.
In fact, something like:
Upstream: upstream dead, taken from fork at https://github.com/badoo/php-lua/pull/8
is IMO a lot more useful.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-08-13 10:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-06 20:42 [Buildroot] [PATCH v2] package/php-lua: fix build with PHP8/GCC14 Alexis Lothoré via buildroot
2025-08-09 20:42 ` Romain Naour via buildroot
2025-08-11 5:24 ` Alexis Lothoré via buildroot
2025-08-13 10:43 ` Thomas Petazzoni via buildroot [this message]
2025-08-13 16:13 ` Alexis Lothoré 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=20250813124353.4015c466@windsurf \
--to=buildroot@buildroot.org \
--cc=alexis.lothore@bootlin.com \
--cc=herve.codina@bootlin.com \
--cc=nicolas.carrier@nav-timing.safrangroup.com \
--cc=romain.naour@smile.fr \
--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