Lines Matching refs:history

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