Lines Matching refs:tree

38 the tree, use branches, etc.  An understanding of git's tools for the
78 turning a tested (hopefully) kernel tree into an untested one.  But, beyond
91 an exported tree.  Moving changesets between trees to avoid conflicts in
97 As the mainline (or other tree upon which a set of changes is based)
98 advances, it is tempting to merge with that tree to stay on the leading
100 another tree, but rebasing is not an option once a tree is exported to the
114 thing happening; putting up a git tree with unreviewed or off-topic patches
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
129 right, request that the tree be included in linux-next.
131 If and when others start to send patches for inclusion into your tree,
138 your tree is, what branch to pull, and what changes will result from the