[Buildroot] [PATCH v2 1/3] docs/manual: rewrite section for upstream documentation

Peter Korsgaard peter at korsgaard.com
Sun Apr 23 09:43:20 UTC 2023


>>>>> "Vincent" == Vincent Fazio <vfazio at 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 at gmail.com>
 > ---
 > Changes v1 -> v2:
 >   - Minor updates commit message body

Committed to 2023.02.x, thanks.

-- 
Bye, Peter Korsgaard



More information about the buildroot mailing list