davidlt/kernel-ark
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Create home

Jeremy Cline 2019-10-09 13:48:49 +00:00
commit 0f3ca82628
1 changed files with 36 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

36
home.md Normal file

@ -0,0 +1,36 @@
This guide covers setting up a development environment, the repository layout, and the general contribution workflow.
## Setup
To start with you need to:
1. Make a [GitLab account](https://gitlab.com/users/sign_in#register-pane) if you do not already have one.
2. Fork the [ARK tree](https://gitlab.com/cki-project/kernel-ark) (click the fork button in the upper right-hand corner and wait patiently).
Once GitLab finishes forking the repository (this can take a while):
1. ``git clone git@gitlab.com:<your gitlab name>/kernel-ark.git && cd kernel-ark``
2. ``git remote add -f linus git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git``
3. ``git remote add -f upstream https://gitlab.com/cki-project/kernel-ark.git``
## Branches
### master
The master branch points to the latest ARK branch.
### internal
The internal branch is used for the kernel configuration and build scripts. When new configuration options are needed or the build requirements change, this is the branch to send merge requests to. When a new release is made, this branch is merged into the release branch. Configuration and build scripts can be found in the ``redhat/`` directory.
### rhpatches
This branch tracks the latest version of the kernel patches for ARK.
### Release branches
Each time the kernel is rebased, a set of branches is created to track that release. The branch format for releases is ``ark/<upstream tag>``.
#### ark/vX.Y[-rcN]
Branches in this format (e.g. ``ark/v5.4-rc1`` or ``ark/v5.3``) contain the set of patches that were added on top of the upstream kernel release along with the configuration and build scripts. They can be checked out and built into RPMs.