Lines Matching refs:changes
41 of the mainline repository, explore the revision history, commit changes to
81 Rewriting history will rewrite the changes contained in that history,
90 So, once you push a set of changes to your publicly-available server, those
91 changes should not be rewritten. Git will attempt to enforce this rule if
92 you try to push changes which do not result in a fast-forward merge
93 (i.e. changes which do not share the same history). It is possible to
101 As the mainline (or other tree upon which a set of changes is based)
109 release). If you are nervous about specific changes, you can always
116 slip in ill-advised changes which go into the mainline below the review
132 should not be making changes to the core memory management code. And, most
144 your tree is, what branch to pull, and what changes will result from the
147 sure that you have remembered to push those changes to the public server.
176 documentation, adverse effects on performance, user-space ABI changes, etc.