Go to file
Giulio Benetti de349df08c docs/manual: add section to explain how to give credits to a sponsor
Sometimes it happens that a Company or a Physical Person sponsors the
creation and/or the upstreaming process of a patch, but at the moment
there is no way to give credits to it. In Linux they prepend '+sponsor'
to the e-mail of the contributor in both authorship and commit log tag as
discussed here[0]. So let's describe in the manual how to do that as a
standard.

[0]: https://lore.kernel.org/linux-doc/20230817220957.41582-1-giulio.benetti@benettiengineering.com/

Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
[yann.morin.1998@free.fr:
  - reword to reference sub-addressing and the RFC
  - move to the "submitting patches" section, that already deals with
    SoB tags
  - differentiate between Your/Their names
]
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2023-09-21 23:57:26 +02:00
arch
board board/orangepi*: update links in readme files 2023-09-16 16:45:14 +02:00
boot Merge branch 'next' 2023-09-07 16:50:14 +02:00
configs configs/roc_pc_rk3399: enable OpenSSL for U-Boot 2023-09-20 22:34:23 +02:00
docs docs/manual: add section to explain how to give credits to a sponsor 2023-09-21 23:57:26 +02:00
fs
linux
package package/swupdate: fix musl build 2023-09-21 21:43:31 +02:00
support support/testing/tests/package/test_tcl.py: new runtime test 2023-09-17 22:09:40 +02:00
system
toolchain Merge branch 'next' 2023-09-07 16:50:14 +02:00
utils utils/getdeveloperlib.py: handle file removal 2023-09-11 22:08:22 +02:00
.checkpackageignore package/tcl: fix package patch 2023-09-21 20:49:26 +02:00
.clang-format
.defconfig
.flake8
.gitignore
.gitlab-ci.yml
.shellcheckrc
CHANGES Update for 2023.08 2023-09-06 21:54:35 +02:00
Config.in
Config.in.legacy
COPYING
DEVELOPERS support/testing/tests/package/test_tcl.py: new runtime test 2023-09-17 22:09:40 +02:00
Makefile Merge branch 'next' 2023-09-07 16:50:14 +02:00
Makefile.legacy
README

Buildroot is a simple, efficient and easy-to-use tool to generate embedded
Linux systems through cross-compilation.

The documentation can be found in docs/manual. You can generate a text
document with 'make manual-text' and read output/docs/manual/manual.text.
Online documentation can be found at http://buildroot.org/docs.html

To build and use the buildroot stuff, do the following:

1) run 'make menuconfig'
2) select the target architecture and the packages you wish to compile
3) run 'make'
4) wait while it compiles
5) find the kernel, bootloader, root filesystem, etc. in output/images

You do not need to be root to build or run buildroot.  Have fun!

Buildroot comes with a basic configuration for a number of boards. Run
'make list-defconfigs' to view the list of provided configurations.

Please feed suggestions, bug reports, insults, and bribes back to the
buildroot mailing list: buildroot@buildroot.org
You can also find us on #buildroot on OFTC IRC.

If you would like to contribute patches, please read
https://buildroot.org/manual.html#submitting-patches