.gitignore
Makefile.rhelver
Module.kabi_aarch64
Module.kabi_dup_aarch64
Module.kabi_dup_ppc64le
Module.kabi_dup_s390x
Module.kabi_dup_x86_64
Module.kabi_ppc64le
Module.kabi_s390x
Module.kabi_x86_64
README.rst
def_variants.yaml.fedora
def_variants.yaml.rhel
dracut-virt.conf
flavors
gating.yaml
kernel-aarch64-16k-debug-fedora.config
kernel-aarch64-16k-fedora.config
kernel-aarch64-64k-debug-rhel.config
kernel-aarch64-64k-rhel.config
kernel-aarch64-debug-fedora.config
kernel-aarch64-debug-rhel.config
kernel-aarch64-fedora.config
kernel-aarch64-rhel.config
kernel-aarch64-rt-debug-rhel.config
kernel-aarch64-rt-rhel.config
kernel-local
kernel-ppc64le-debug-fedora.config
kernel-ppc64le-debug-rhel.config
kernel-ppc64le-fedora.config
kernel-ppc64le-rhel.config
kernel-s390x-debug-fedora.config
kernel-s390x-debug-rhel.config
kernel-s390x-fedora.config
kernel-s390x-rhel.config
kernel-s390x-zfcpdump-rhel.config
kernel-x86_64-debug-fedora.config
kernel-x86_64-debug-rhel.config
kernel-x86_64-fedora.config
kernel-x86_64-rhel.config
kernel-x86_64-rt-debug-rhel.config
kernel-x86_64-rt-rhel.config
kernel.changelog
kernel.spec
kvm_stat.logrotate
linux-kernel-test.patch
partial-clang-debug-snip.config
partial-clang-snip.config
partial-clang_lto-aarch64-debug-snip.config
partial-clang_lto-aarch64-snip.config
partial-clang_lto-x86_64-debug-snip.config
partial-clang_lto-x86_64-snip.config
partial-kgcov-debug-snip.config
partial-kgcov-snip.config
patch-6.10-redhat.patch
redhatsecureboot501.cer
redhatsecurebootca5.cer
rpminspect.yaml
sources
x509.genkey.centos
x509.genkey.fedora
x509.genkey.rhel
check-kabi
filtermods.py
generate_all_configs.sh
merge.py
mod-denylist.sh
mod-sign.sh
process_configs.sh
README.rst

The Kernel dist-git

The kernel is maintained in a source tree rather than directly in dist-git. The specfile is maintained as a template in the source tree along with a set of build scripts to generate configurations, (S)RPMs, and to populate the dist-git repository.

The documentation for the source tree covers how to contribute and maintain the tree.

If you're looking for the downstream patch set it's available in the source tree with "git log master..ark-patches" or online.

Each release in dist-git is tagged in the source repository so you can easily check out the source tree for a build. The tags are in the format name-version-release, but note release doesn't contain the dist tag since the source can be built in different build roots (Fedora, CentOS, etc.)