Lines Matching full:git

11 Managing patches with git
20 BitKeeper.  For better or for worse, the kernel project has settled on git
23 Managing patches with git can make life much easier for the developer,
24 especially as the volume of those patches grows.  Git also has its rough
27 teach the reader how to use git; that would be sufficient material for a
28 long document in its own right.  Instead, the focus here will be on how git
30 wish to come up to speed with git will find more information at:
32 	https://git-scm.com/
34 	https://www.kernel.org/pub/software/scm/git/docs/user-manual.html
39 understanding of how git works before trying to use it to make patches
40 available to others.  A git-using developer should be able to obtain a copy
42 the tree, use branches, etc.  An understanding of git's tools for the
43 rewriting of history (such as rebase) is also useful.  Git comes with its
44 own terminology and concepts; a new user of git should know about refs,
49 Using git to generate patches for submission by email can be a good
52 When you are ready to start putting up git trees for others to look at, you
54 server with git-daemon is relatively straightforward if you have a system
60 The normal git workflow involves the use of a lot of branches.  Each line
62 maintained independently.  Branches in git are cheap, there is no reason to
69 Git provides some powerful tools which can allow you to rewrite your
75 shifted from one branch to another.  And so on.  Judicious use of git's
91 changes should not be rewritten.  Git will attempt to enforce this rule if
110 perform test merges in a private branch.  The git "rerere" tool can be
114 One of the biggest recurring complaints about tools like git is this: the
118 thing happening; putting up a git tree with unreviewed or off-topic patches
123 	You can send me patches, but for me to pull a git patch from you, I
133 importantly, do not use a git tree to bypass the review process.  Post an
139 authorship information; the git "am" tool does its best in this regard, but
145 pull.  The git request-pull command can be helpful in this regard; it will