How to more easily view the Linux kernel code update record "Go"

Transferred from: http://blog.csdn.net/lee244868149/article/details/44302819

Linux kernel update is very fast, how to quickly understand these updates? The most common way is to download the old and new version of the kernel source code, and then use Bcompare or other tools for source comparison, but this is obviously more laborious and time-consuming, and this article will introduce a faster and simpler method.

On the official http://git.kernel.org/website you can find various git update records for Linux, such as Virt/kvm/kvm.git, which can be seen in various updates of KVM.

Looking at the update of the Linux 2.6 kernel we are focusing on, we know that the Linux 2.6 kernel is maintained by Linus, so the corresponding Git link is: linux/kernel/git/torvalds/ Linux-2.6.git, from the display, this and another link linux/kernel/git/torvalds/linux.git has no difference, it is estimated that the introduction of the Linux 3.x version and version of the warehouse management has been improved and optimized, It doesn't matter, however, that we continue to understand this official web git library.

First, find the corresponding version of our concern, this on the Linux/kernel/git/torvalds/linux-2.6.git page click on the tags link to go to all the version list, http://git.kernel.org/?p=linux/ Kernel/git/torvalds/linux-2.6.git;a=tags, open the interface as follows:

On this page you can find the corresponding version, in 2.6.38.8, for example, the corresponding entry is the Linux 2.6.38-rc8:

There are several links here, but a few points will be found in the chain to the same place, so we directly see the fastest path, shortlog and log, the two links open after the display is a modification of the log, but the Shortlog display is relatively compact. Point Open Shortlog:

Click on the first entry:
2011-03-08 Linus Torvalds Linux 2.6.38-rc8 V2.6.38-rc8 Commit | Commitdiff | Tree | Snapsho
Tree link, where you can see all of 2.6.38.8 's final code, which is consistent with the code downloaded from http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.38.8.tar.bz2.
Let's take an example to see what's going on with the NMI to 2.6.38.8 version.
Follow the "[Linux/kernel/git/torvalds/linux-2.6.git]/arch/x86/include/asm/" one-way link to get down here:

Locate the Nmi.h file (this file is associated with the NMI) entry, and click on the following history link:

As you can see, all the changes from 2008-10-23 to the current version have been made. For example, the first entry in 2011-01-07 to the NMI to commit the changes, the following Commitdiff is the submission of the updated content, diff to the current of course not, because nature is commitdiff consistent, and other items need diff to the current , because their commitdiff is different from the later version, and the diff to current is different for Linux 2.6.38-rc8, if you want to see all the updates from 2008-10-23 to Linux 2.6.38-rc8, Just click the diff to current link for this entry in 2008-10-23.

The above example is relatively simple, I also said more rough, mainly because the link is very much, a description of the more trouble, too many stickers are just a waste of my personal site server space, the best way is to do their own to point the link, check the content, a few rounds will definitely be able to explore a clear one or two.

Reprint please keep address: http://www.lenky.info/archives/2012/07/1782 or http://lenky.info/?p=1782

Note: If no special instructions, the content of the article is from the lenky of the true understanding of the individual and not deliberately self-speculation to deliberate fools eyes and ears. Due to the limited personal level, although the content is correct, but still inevitably error, please do not take offense, if you can leave a message, and welcome letter to discuss. In addition, it is worth noting that some of Lenky's articles, as well as some of the content of reference to the network of Friends of the enthusiastic sharing, especially some with a full reference to the article, the accompanying link may be more direct and richer, and I just did a summary & reporting, in this also expressed thanks. About this site all technical articles, welcome reprint, but please follow the CC creative sharing agreement, and some of the more private nature of the mood essay, it is recommended not reproduced.

Law: According to the newly promulgated "Information Network dissemination right protection regulations", if you believe that any content of this article infringes your rights, please notify by email or in writing, the site will promptly delete the relevant content or links.

How to more easily view the Linux kernel code update record "Go"