Lines Matching +full:pulled +full:- +full:up

12 -------------------------
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
40 available to others.  A git-using developer should be able to obtain a copy
45 remote branches, the index, fast-forward merges, pushes and pulls, detached
50 exercise while coming up to speed.
52 When you are ready to start putting up git trees for others to look at, you
53 will, of course, need a server that can be pulled from.  Setting up such a
54 server with git-daemon is relatively straightforward if you have a system
65 Publicly-available branches should be created with care; merge in patches
66 from development branches when they are in complete form and ready to go -
85 have pulled into their repositories, you will make life much more difficult
90 So, once you push a set of changes to your publicly-available server, those
92 you try to push changes which do not result in a fast-forward merge
96 linux-next is one example.  But such actions should be rare.  This is one
103 edge.  For a private branch, rebasing can be an easy way to keep up with
108 generally only at specific release points (such as a mainline -rc
116 slip in ill-advised changes which go into the mainline below the review
118 thing happening; putting up a git tree with unreviewed or off-topic patches
119 can affect your ability to get trees pulled in the future.  Quoting Linus:
135 right, request that the tree be included in linux-next.
145 pull.  The git request-pull command can be helpful in this regard; it will
152 -----------------
163 developer who may well feel nervous about questioning code - in public -
183 documentation, adverse effects on performance, user-space ABI changes, etc.
187 There is no strict requirement to use specific tags like ``Reviewed-by``.