hc
2023-12-11 d2ccde1c8e90d38cee87a1b0309ad2827f3fd30d
kernel/Documentation/process/7.AdvancedTopics.rst
....@@ -29,9 +29,9 @@
2929 fits into the kernel development process in particular. Developers who
3030 wish to come up to speed with git will find more information at:
3131
32
- http://git-scm.com/
32
+ https://git-scm.com/
3333
34
- http://www.kernel.org/pub/software/scm/git/docs/user-manual.html
34
+ https://www.kernel.org/pub/software/scm/git/docs/user-manual.html
3535
3636 and on various tutorials found on the web.
3737
....@@ -55,7 +55,7 @@
5555 which is accessible to the Internet. Otherwise, free, public hosting sites
5656 (Github, for example) are starting to appear on the net. Established
5757 developers can get an account on kernel.org, but those are not easy to come
58
-by; see http://kernel.org/faq/ for more information.
58
+by; see https://kernel.org/faq/ for more information.
5959
6060 The normal git workflow involves the use of a lot of branches. Each line
6161 of development can be separated into a separate "topic branch" and
....@@ -125,7 +125,7 @@
125125 to trust things *without* then having to go and check every
126126 individual change by hand.
127127
128
-(http://lwn.net/Articles/224135/).
128
+(https://lwn.net/Articles/224135/).
129129
130130 To avoid this kind of situation, ensure that all patches within a given
131131 branch stick closely to the associated topic; a "driver fixes" branch