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: Wed, 29 Mar 2023 10:50:22 +0200 [thread overview]
Message-ID: <20230329105022.6137bf1a@windsurf> (raw)
In-Reply-To: <c7968ace-cfbb-1c54-bdde-083a37423686@mind.be>
On Wed, 29 Mar 2023 10:44:38 +0200
Arnout Vandecappelle <arnout@mind.be> wrote:
> > Note: if the path header has the upstream commit sha1 and applies as-is
> > (possibly with just a bit of fuzz), then "backport from upstream" is
> > enough. But if you had to rewrite the ptch, and the header does not have
> > the upstream sha1, then add it to the note:
> >
> > [yann.morin.1998@free.fr: backport and adapt from upsteam 1234CDEF]
>
> So this would be
>
> Upstream: backport from 1234CDEF [yann.morin.1998@free.fr]
If we standardize in a format, then it should handle all common
situations. A patch being a backport from an upstream commit is one
situation. But here are several more situations:
- Patch taken from the upstream project, but not merged yet (from a
pull request, a mail on a mailing list, etc.)
- Patch taken from a downstream distribution (Debian, Gentoo, Alpine
Linux, etc.)
- Patch submitted upstream by us, but not merged yet (quite similar to
case 1 above)
- Patch not submitted upstream for reason XYZ
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-29 8:50 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 [this message]
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
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=20230329105022.6137bf1a@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.