[lkml]   [2016]   [Oct]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Patch in this message
Subject[PATCH net-next] Documentation/networking: update git urls to use https over http
This fixes the following errors when trying to clone the urls:

Cloning into 'net'...
fatal: repository '' not found
Cloning into 'net-next'...
fatal: repository '' not found
Cloning into 'linux'...
fatal: repository '' not found
Cloning into 'stable-queue'...
fatal: repository '' not found

Signed-off-by: Alexander Alemayhu <>
Documentation/networking/netdev-FAQ.txt | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/Documentation/networking/netdev-FAQ.txt b/Documentation/networking/netdev-FAQ.txt
index 0fe1c6e0dbcd..a20b2fae942b 100644
--- a/Documentation/networking/netdev-FAQ.txt
+++ b/Documentation/networking/netdev-FAQ.txt
@@ -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:


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:


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:

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.
 \ /
  Last update: 2016-10-13 17:11    [W:0.032 / U:0.728 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site