From: Peter Korsgaard <peter@korsgaard.com>
To: Vincent Fazio <vfazio@gmail.com>
Cc: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>,
Ricardo Martincoski <ricardo.martincoski@datacom.com.br>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/3] docs/manual: rewrite section for upstream documentation
Date: Sun, 23 Apr 2023 11:43:20 +0200 [thread overview]
Message-ID: <877cu36iiv.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20230403144105.419341-1-vfazio@gmail.com> (Vincent Fazio's message of "Mon, 3 Apr 2023 09:41:03 -0500")
>>>>> "Vincent" == Vincent Fazio <vfazio@gmail.com> writes:
> Previously, the documentation only requested links to upstream commits
> when backporting patches.
> Based on a mailing list discussion [0], patches should, when possible
> and when approriate, provide a link as evidence that the patch has been
> submitted upstream.
> The motivation is that hopefully the patch gets applied to upstream at
> some point reducing the long term maintenance burden within Buildroot.
> This also makes future patch review on subsequent package version bumps
> more streamlined.
> For patches that are unique to BR and do not apply to the upstream
> repository, patches should have a comment explaining why they do not
> apply upstream.
> [0] https://lists.buildroot.org/pipermail/buildroot/2023-March/666000.html
> Signed-off-by: Vincent Fazio <vfazio@gmail.com>
> ---
> Changes v1 -> v2:
> - Minor updates commit message body
Committed to 2023.02.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-04-23 9:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 14:41 [Buildroot] [PATCH v2 1/3] docs/manual: rewrite section for upstream documentation Vincent Fazio
2023-04-03 14:41 ` [Buildroot] [PATCH v2 2/3] utils/checkpackagelib: check for Upstream trailers Vincent Fazio
2023-04-03 14:41 ` [Buildroot] [PATCH v2 3/3] .checkpackageignore: add entries missing Upstream trailer Vincent Fazio
2023-04-15 17:54 ` [Buildroot] [PATCH v2 1/3] docs/manual: rewrite section for upstream documentation Yann E. MORIN
2023-04-23 9:43 ` Peter Korsgaard [this message]
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=877cu36iiv.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=ricardo.martincoski@datacom.com.br \
--cc=thomas.de_schampheleire@nokia.com \
--cc=vfazio@gmail.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