Lines Matching refs:changes

37 of the mainline repository, explore the revision history, commit changes to
77 Rewriting history will rewrite the changes contained in that history,
86 So, once you push a set of changes to your publicly-available server, those
87 changes should not be rewritten.  Git will attempt to enforce this rule if
88 you try to push changes which do not result in a fast-forward merge
89 (i.e. changes which do not share the same history).  It is possible to
97 As the mainline (or other tree upon which a set of changes is based)
105 release).  If you are nervous about specific changes, you can always
112 slip in ill-advised changes which go into the mainline below the review
126 should not be making changes to the core memory management code.  And, most
138 your tree is, what branch to pull, and what changes will result from the
141 sure that you have remembered to push those changes to the public server.
169 documentation, adverse effects on performance, user-space ABI changes, etc.