Lines Matching refs:can

5 number of topics which can be helpful for developers wanting to become a
19 Managing patches with git can make life much easier for the developer,
42 heads, etc.  It can all be a little intimidating at the outset, but the
45 Using git to generate patches for submission by email can be a good
49 will, of course, need a server that can be pulled from.  Setting up such a
53 developers can get an account on kernel.org, but those are not easy to come
57 of development can be separated into a separate "topic branch" and
65 Git provides some powerful tools which can allow you to rewrite your
67 say, or which has some other sort of obvious bug) can be fixed in place or
68 made to disappear from the history entirely.  A patch series can be
70 you have been working on it for months.  Changes can be transparently
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
94 can be rewritten if necessary) and only moved into public branches when
99 edge.  For a private branch, rebasing can be an easy way to keep up with
102 makes good sense, but overly frequent merges can clutter the history
105 release).  If you are nervous about specific changes, you can always
106 perform test merges in a private branch.  The git "rerere" tool can be
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
139 pull.  The git request-pull command can be helpful in this regard; it will
151 looking at code you can make a significant contribution to the process as a
154 Reviewing code can be an intimidating prospect, especially for a new kernel
157 the most experienced developers can be improved, though.  Perhaps the best