From ea08eeccae9297f7aabd2ef7f0c2517ac4549acc Mon Sep 17 00:00:00 2001 From: hc <hc@nodka.com> Date: Tue, 20 Feb 2024 01:18:26 +0000 Subject: [PATCH] write in 30M --- kernel/Documentation/process/7.AdvancedTopics.rst | 8 ++++---- 1 files changed, 4 insertions(+), 4 deletions(-) diff --git a/kernel/Documentation/process/7.AdvancedTopics.rst b/kernel/Documentation/process/7.AdvancedTopics.rst index 172733c..bf7cbfb 100644 --- a/kernel/Documentation/process/7.AdvancedTopics.rst +++ b/kernel/Documentation/process/7.AdvancedTopics.rst @@ -29,9 +29,9 @@ fits into the kernel development process in particular. Developers who wish to come up to speed with git will find more information at: - http://git-scm.com/ + https://git-scm.com/ - http://www.kernel.org/pub/software/scm/git/docs/user-manual.html + https://www.kernel.org/pub/software/scm/git/docs/user-manual.html and on various tutorials found on the web. @@ -55,7 +55,7 @@ which is accessible to the Internet. Otherwise, free, public hosting sites (Github, for example) are starting to appear on the net. Established developers can get an account on kernel.org, but those are not easy to come -by; see http://kernel.org/faq/ for more information. +by; see https://kernel.org/faq/ for more information. The normal git workflow involves the use of a lot of branches. Each line of development can be separated into a separate "topic branch" and @@ -125,7 +125,7 @@ to trust things *without* then having to go and check every individual change by hand. -(http://lwn.net/Articles/224135/). +(https://lwn.net/Articles/224135/). To avoid this kind of situation, ensure that all patches within a given branch stick closely to the associated topic; a "driver fixes" branch -- Gitblit v1.6.2