mirror of
https://source.denx.de/u-boot/u-boot.git
synced 2026-06-13 15:03:58 +03:00
Merge tag 'v2024.10-rc5' into next
Prepare v2024.10-rc5
This commit is contained in:
@@ -23,9 +23,8 @@ Management Summary
|
||||
Phases of the Development Process
|
||||
---------------------------------
|
||||
|
||||
U-Boot development takes place in `Release Cycles
|
||||
<https://www.denx.de/wiki/U-Boot/ReleaseCycle>`_. A Release Cycle lasts
|
||||
normally for three months.
|
||||
U-Boot development takes place in a :doc:`release_cycle`. A Release Cycle
|
||||
lasts normally for three months.
|
||||
|
||||
The first three weeks of each Release Cycle are called *Merge Window*.
|
||||
|
||||
|
||||
@@ -73,12 +73,13 @@ General Patch Submission Rules
|
||||
cover letter why they are ignored is desired.
|
||||
|
||||
* Send your patches as plain text messages: no HTML, no MIME, no links, no
|
||||
compression, no attachments. Just plain text. The best way the generate
|
||||
patches is by using the ``git format-patch`` command. Please use the
|
||||
``master`` branch of the mainline U-Boot git repository
|
||||
(``https://source.denx.de/u-boot/u-boot.git``) as reference, unless (usually
|
||||
late in a release cycle) there has been an announcement to use the ``next``
|
||||
branch of this repository instead.
|
||||
compression, no attachments. Just plain text. The best way to generate
|
||||
patches is by using the ``git format-patch`` command. For a patch that is
|
||||
fixing a bug or regression of some sort, please use the ``master`` branch of
|
||||
the mainline U-Boot git repository located at
|
||||
https://source.denx.de/u-boot/u-boot.git as reference. For new features, if
|
||||
the ``next`` branch has been opened (which happens with the release of
|
||||
``-rc2``) that branch should be used, otherwise ``master`` is acceptable.
|
||||
|
||||
* Make sure that your mailer does not mangle the patch by automatic changes
|
||||
like wrapping of longer lines etc.
|
||||
|
||||
@@ -9,7 +9,7 @@ release that came out in October 2020. Release candidates are tagged every few
|
||||
weeks as the project heads to the next release. So 2020.10-rc1 was the first
|
||||
release candidate (RC), tagged soon after 2020.07 was released.
|
||||
|
||||
See https://www.denx.de/wiki/view/U-Boot/ReleaseCycle for full details.
|
||||
See :doc:`release_cycle` for full details.
|
||||
|
||||
Within the build system, various Makefile variables are created, making use of
|
||||
VERSION, PATCHLEVEL and EXTRAVERSION defined at the top of 'Makefile'. There is
|
||||
|
||||
Reference in New Issue
Block a user