|
@@ -29,8 +29,8 @@ A: There are always two trees (git repositories) in play. Both are driven
|
|
|
Linus, and net-next is where the new code goes for the future release.
|
|
|
You can find the trees here:
|
|
|
|
|
|
- http://git.kernel.org/?p=linux/kernel/git/davem/net.git
|
|
|
- http://git.kernel.org/?p=linux/kernel/git/davem/net-next.git
|
|
|
+ https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git
|
|
|
+ https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git
|
|
|
|
|
|
Q: How often do changes from these trees make it to the mainline Linus tree?
|
|
|
|
|
@@ -76,7 +76,7 @@ Q: So where are we now in this cycle?
|
|
|
|
|
|
A: Load the mainline (Linus) page here:
|
|
|
|
|
|
- http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git
|
|
|
+ https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
|
|
|
|
|
|
and note the top of the "tags" section. If it is rc1, it is early
|
|
|
in the dev cycle. If it was tagged rc7 a week ago, then a release
|
|
@@ -123,7 +123,7 @@ A: Normally Greg Kroah-Hartman collects stable commits himself, but
|
|
|
|
|
|
It contains the patches which Dave has selected, but not yet handed
|
|
|
off to Greg. If Greg already has the patch, then it will be here:
|
|
|
- http://git.kernel.org/cgit/linux/kernel/git/stable/stable-queue.git
|
|
|
+ https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git
|
|
|
|
|
|
A quick way to find whether the patch is in this stable-queue is
|
|
|
to simply clone the repo, and then git grep the mainline commit ID, e.g.
|