Re: [Buildroot] Indicating upstream status [was: [PATCH] package/bluez5_utils: Fix builds with musl-libc]

[Thomas Petazzoni via buildroot <buildroot@buildroot.org>]

On Thu, 30 Mar 2023 09:03:50 +0200
Arnout Vandecappelle <arnout@mind.be> wrote:

>   That's where I got my inspiration :-) I just find "Upstream-status" a bit 
> long, so I abbreviated it to "Upstream". Also, "Submitted" and "Accepted" are 
> not really useful because the upstream status is going to change while we don't 
> change our patch. In addition, a simple URL there is enough information. That's 
> how I got to:
> 
> For Submitted/Accepted:
> Upstream: <PR/mailing list/patchwork URL>
> 
> For Backport/Accepted:
> Upstream: <commit hash> [submitter@email.address]
> 
> For Denied:
> Upstream: Denied <PR/mailing list/patchwork URL>
> 
> For Inappropriate:
> Upstream: N/A + explanation why
> 
>   Only "Pending" is a little iffy - we just don't want "Pending" patches I guess.

This sounds good to me.

For the Backport/Accepted, I tend to like when it's the URL to the
commit on Github/Gitlab/Git repo rather than just the hash because then
I can just click on it and see the patch. Also who would be the
[submitter@email.address] in this case? The author of the upstream
patch? Why do we need to replicate that information in Buildroot?

Best regards,

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