From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
marcin@bis.org.pl, d.lang@abatec.at, buildroot@buildroot.org,
"Yann E. MORIN" <yann.morin.1998@free.fr>
Subject: Re: [Buildroot] Indicating upstream status [was: [PATCH] package/bluez5_utils: Fix builds with musl-libc]
Date: Thu, 30 Mar 2023 14:21:33 +0200 [thread overview]
Message-ID: <20230330142133.002fa797@windsurf> (raw)
In-Reply-To: <84821597-4e34-2e1c-99f5-4d03bdda0d45@mind.be>
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
next prev parent reply other threads:[~2023-03-30 12:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-26 13:09 [Buildroot] [PATCH] package/bluez5_utils: Fix builds with musl-libc Florian Fainelli
2023-03-28 20:25 ` Yann E. MORIN
2023-03-29 8:44 ` [Buildroot] Indicating upstream status [was: [PATCH] package/bluez5_utils: Fix builds with musl-libc] Arnout Vandecappelle
2023-03-29 8:50 ` Thomas Petazzoni via buildroot
2023-03-29 9:06 ` Arnout Vandecappelle
2023-03-29 9:28 ` Thomas Petazzoni via buildroot
2023-03-29 12:39 ` Florian Fainelli
2023-03-30 7:03 ` Arnout Vandecappelle
2023-03-30 12:21 ` Thomas Petazzoni via buildroot [this message]
2023-03-30 12:33 ` Arnout Vandecappelle
2023-03-31 7:28 ` Thomas Petazzoni 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=20230330142133.002fa797@windsurf \
--to=buildroot@buildroot.org \
--cc=arnout@mind.be \
--cc=d.lang@abatec.at \
--cc=f.fainelli@gmail.com \
--cc=marcin@bis.org.pl \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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.