McKenney 25 min. Paul E. Unnamed repository; edit this file 'description' to name the repository. Raw logs of warnings of Sparse running on the kernel with summary logs. POSIX manual pages - sections 0p, 1p, 3p. Build framework and autorun scripts for xfstests. Filesystem-level encryption kernel development tree.
A copy of sha1collisiondetection by Marc Stevens for use by the git. Gitolite transparency log to Gitolite transparency log - current. A library for direct userspace access to InfiniBand hardware. C library and tools for interacting with the linux GPIO character device. Library to parse raw trace event formats. Python interface for the Linux scheduler functions etc. Staging tree for Linux LoRa sockets. Andreas Gruenbacher's fork of linux. Bjorn Andersson's fork of linux.
Kernel tree that adds features to make rootkits harder to productize. Fun projects that arnd has been hacking on. Arne's btrfs-progs development tree. Automatically backports the Linux kernel. Historical - v3. Historical - v2. Benjamin Herrenschmidt's fork of linux. Collection of patches waiting for integration. Bluetooth kernel development tree. Christian Borntraeger's fork of linux. Miscelaneous changes for trees other than mine.
Voltage and current regulator API. Linux kernel tree for Loongson. Civil Infrastructure Platform stable kernel branches. Realtime Kernel performance evaluator. Support for the Tilera 'tile' architecture. Chris Zankel's fork of linux. Exynos DRM Framework and relevant drivers. Daniel Phillips's fork of linux. Linux Chromebook Pixel Drivers.
Collection of prtconf output for various Sparc systems. Split device-tree repository -- potentially rebasing. CacheFiles management daemon package. MN architecture changes. Keyrings patches on top of James's security tree.
Rebasing repository for the development of interfaces for controlling namespaces User namespace aka uid 0! Userspace utilities for fs-verity. Eric Biggers's fork of xfsprogs-dev. Eric Biggers's fork of xfstests-dev. Linux Tree for SoC's Thermal. Repository of firmware blobs for use with the Linux kernel. Renesas Kernel Drivers Development Tree.
Driver core development git tree. Greg Kroah-Hartman's fork of kexec-tools. Gustavo A. Jesper Brouer's fork of net-next. Backports of Renesas Drivers and Platforms. No-history klibc kernel tree. Generate x86 system call tables. Civil Infrastructure Platform development kernel branches. Nobuhiro Iwamatsu's fork of linux-rt-devel. Toshiba Visconti ARM sub-architecture kernel tree.
Intel wireless group's fork of linux. Userland tools for the f2fs filesystem. Staging tree to send pull requests to Linus. Jeffrey Mahoney's fork of linux Osmand r2. UEFI enhancements for Galileo developer board. Asterisk web integration for Aastra phones. Enhancements to impress. PKCS11 software token exporting openssl keys including engine keys. TPM2 engine and key creation tools for openssl.
Main branches are for-next, fixes and topic. SCSI development tree see misc fixes and for-next branches. Preload library for activating secret memory.
Jes Sorensen's fork of fsverity-utils. Legacy metag platform support tree. You can switch to any previously released kernel version using the release tags. Maintaining local changes During development, the kernel git repository is being constantly rebased against Linus' tree. IOW, Ubuntu specific changes are not being merged , but rather popped off, the tree updated to mainline, and then the Ubuntu specific changes reapplied; they are rebased.
The output from this command can then be sent to the kernel-team mailing list. Alternatively, if you have a publicly available git repository for which changes can be pulled from, you can use git request-pull to generate an email message to send to the kernel-team mailing list. The commit templates contain comments for how to fill out the required information. Also note that all commits must have a Signed-off-by line the "-s" option to git commit.
The primary one you will use is the patch template. It is commented heavily, so should be self explanatory. Some templates do not require editing such as the bumpabi and updateconfigs templates. The prefix for the line defines the type of the commit see below. The last line should contain your sign-off for the patch and any acks it has received. This book was written using Git version 2. Since Git is quite excellent at preserving backwards compatibility, any version after 2.
If you want to install the basic Git tools on Linux via a binary installer, you can generally do so through the package management tool that comes with your distribution. There are several ways to install Git on a Mac. The easiest is probably to install the Xcode Command Line Tools. On Mavericks If you want a more up to date version, you can also install it via a binary installer.
There are also a few ways to install Git on Windows. The most official build is available for download on the Git website. To get an automated installation you can use the Git Chocolatey package.
0コメント