Lines Matching refs:to
4 works. There is still more to learn, however! This section will cover a
5 number of topics which can be helpful for developers wanting to become a
12 application. While BitKeeper was controversial, the approach to software
15 project. In current times, there are several free alternatives to
22 still being civilized by its developers. This document will not attempt to
23 teach the reader how to use git; that would be sufficient material for a
26 wish to come up to speed with git will find more information at:
34 The first order of business is to read the above sites and get a solid
35 understanding of how git works before trying to use it to make patches
36 available to others. A git-using developer should be able to obtain a copy
37 of the mainline repository, explore the revision history, commit changes to
43 concepts are not that hard to grasp with a bit of study.
45 Using git to generate patches for submission by email can be a good
46 exercise while coming up to speed.
48 When you are ready to start putting up git trees for others to look at, you
51 which is accessible to the Internet. Otherwise, free, public hosting sites
52 (Github, for example) are starting to appear on the net. Established
53 developers can get an account on kernel.org, but those are not easy to come
58 maintained independently. Branches in git are cheap, there is no reason to
60 development in any branch which you intend to ask others to pull from.
62 from development branches when they are in complete form and ready to go -
65 Git provides some powerful tools which can allow you to rewrite your
68 made to disappear from the history entirely. A patch series can be
71 shifted from one branch to another. And so on. Judicious use of git's
72 ability to revise history can help in the creation of clean patch sets with
75 Excessive use of this capability can lead to other problems, though, beyond
83 which has been exported to others should generally be seen as immutable
86 So, once you push a set of changes to your publicly-available server, those
87 changes should not be rewritten. Git will attempt to enforce this rule if
88 you try to push changes which do not result in a fast-forward merge
89 (i.e. changes which do not share the same history). It is possible to
90 override this check, and there may be times when it is necessary to rewrite
91 an exported tree. Moving changesets between trees to avoid conflicts in
98 advances, it is tempting to merge with that tree to stay on the leading
99 edge. For a private branch, rebasing can be an easy way to keep up with
100 another tree, but rebasing is not an option once a tree is exported to the
103 needlessly. Suggested technique in this case is to merge infrequently, and
108 so that you don't have to do the same work twice.
111 mass movement of patches from one repository to another makes it easy to
113 radar. Kernel developers tend to get unhappy when they see that kind of
115 can affect your ability to get trees pulled in the future. Quoting Linus:
117 You can send me patches, but for me to pull a git patch from you, I
118 need to know that you know what you're doing, and I need to be able
119 to trust things *without* then having to go and check every
125 branch stick closely to the associated topic; a "driver fixes" branch
126 should not be making changes to the core memory management code. And, most
127 importantly, do not use a git tree to bypass the review process. Post an
128 occasional summary of the tree to the relevant list, and, when the time is
131 If and when others start to send patches for inclusion into your tree,
132 don't forget to review them. Also ensure that you maintain the correct
134 you may have to add a "From:" line to the patch if it has been relayed to
137 When requesting a pull, be sure to give all the relevant information: where
138 your tree is, what branch to pull, and what changes will result from the
140 format the request as other developers expect, and will also check to be
141 sure that you have remembered to push those changes to the public server.
146 Some readers will certainly object to putting this section with "advanced
148 reviewing patches. It is certainly true that there is no better way to
149 learn how to program in the kernel environment than by looking at code
151 looking at code you can make a significant contribution to the process as a
170 All types of review, if they lead to better code going into the kernel, are