Lines Matching refs:history
17 development history. Indeed, given the scale of the project, avoiding
25 "Rebasing" is the process of changing the history of a series of commits
36 - Changing the history of a set of patches by fixing (or deleting) broken
39 type of operation will be referred to as "history modification"
43 history; used improperly, it can obscure that history and introduce bugs.
61 - Do not rebase a branch that contains history created by others. If you
63 custodian of their history. You should not change it. With few
65 explicitly reverted rather than disappeared via history modification.
78 - Realize that reparenting a patch series (or making significant history
105 current trunk so that no merge commits appear in the history. The kernel
132 history into your tree, you cannot rebase that branch, even if you
149 Why is that? Back merges will muddy the development history of your own