Lines Matching refs:history
41 of the mainline repository, explore the revision history, commit changes to
43 rewriting of history (such as rebase) is also useful. Git comes with its
70 development history. An inconvenient patch (one which breaks bisection,
72 made to disappear from the history entirely. A patch series can be
76 ability to revise history can help in the creation of clean patch sets with
80 a simple obsession for the creation of the perfect project history.
81 Rewriting history will rewrite the changes contained in that history,
84 view of the project history; if you rewrite history which other developers
86 for those developers. So a simple rule of thumb applies here: history
93 (i.e. changes which do not share the same history). It is possible to
106 makes good sense, but overly frequent merges can clutter the history