diff options
| author | Chris Feyerchak <anonymous.contributor@example.org> | 2017-06-26 18:15:25 +0000 |
|---|---|---|
| committer | Konstantin Ryabitsev <konstantin@linuxfoundation.org> | 2024-10-04 15:47:34 -0400 |
| commit | bc381a951d635987c7a4ffcd8de8797118f6bd3c (patch) | |
| tree | f43f5a88cda55f473a081f275594e1f36d1f939c | |
| parent | a9d4a75e8be85b232a60906d446886d7020c4989 (diff) | |
| download | backports-bc381a951d635987c7a4ffcd8de8797118f6bd3c.tar.gz | |
/* Backports development flow */
| -rw-r--r-- | wiki/Documentation_backports_hacking.mediawiki | 12 |
1 files changed, 7 insertions, 5 deletions
diff --git a/wiki/Documentation_backports_hacking.mediawiki b/wiki/Documentation_backports_hacking.mediawiki index 8503512..75c9a29 100644 --- a/wiki/Documentation_backports_hacking.mediawiki +++ b/wiki/Documentation_backports_hacking.mediawiki @@ -10,8 +10,8 @@ The project aims to optimize the backporting process by not only providing backp = Backports development flow = -The [https://git.kernel.org/cgit/linux/kernel/git/backports/backports.git backports.git] master -development branch always tracks linux-next, allowing it to +The [https://git.kernel.org/cgit/linux/kernel/git/backports/backports.git backports.git] "master" +development branch always tracks "linux-next", allowing it to track all the development trees. This ensures that at the end of each merge window, the state of the backports will be very close to the state of the first release candidate. At this @@ -21,9 +21,11 @@ evaluation period, to the major release, and on to its lifetime as a stable kernel. The backports project thus makes three kinds -of backports releases possible: those derived from linux-next, those -derived from the most recent release candidate if any, and -those derived from recent stable kernels. +of backports releases possible: + +* those derived from linux-next +* those derived from the most recent release candidate (if any) +* those derived from recent stable kernels. = Backports git tree tags and branches = |