.. | .. |
---|
29 | 29 | fits into the kernel development process in particular. Developers who |
---|
30 | 30 | wish to come up to speed with git will find more information at: |
---|
31 | 31 | |
---|
32 | | - http://git-scm.com/ |
---|
| 32 | + https://git-scm.com/ |
---|
33 | 33 | |
---|
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 |
---|
35 | 35 | |
---|
36 | 36 | and on various tutorials found on the web. |
---|
37 | 37 | |
---|
.. | .. |
---|
55 | 55 | which is accessible to the Internet. Otherwise, free, public hosting sites |
---|
56 | 56 | (Github, for example) are starting to appear on the net. Established |
---|
57 | 57 | 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. |
---|
59 | 59 | |
---|
60 | 60 | The normal git workflow involves the use of a lot of branches. Each line |
---|
61 | 61 | of development can be separated into a separate "topic branch" and |
---|
.. | .. |
---|
125 | 125 | to trust things *without* then having to go and check every |
---|
126 | 126 | individual change by hand. |
---|
127 | 127 | |
---|
128 | | -(http://lwn.net/Articles/224135/). |
---|
| 128 | +(https://lwn.net/Articles/224135/). |
---|
129 | 129 | |
---|
130 | 130 | To avoid this kind of situation, ensure that all patches within a given |
---|
131 | 131 | branch stick closely to the associated topic; a "driver fixes" branch |
---|