Q: How do you make your history more useful?
A: The answer lies in rebasing. Rebasing is a technique made popular by git where you rewrite your not-yet-pushed patches so that they apply against the current remote
tip, rather than against the
tipof the repository you happened to last pull. The benefit is that your merge history shows useful merges—merges between major branches—rather than simply every single merge you did with the upstream repository.</p></blockquote>
Making your merge history more useful by rebasing. A concept adopted from Git by Mercurial. Still using Subversion? Move on boy. Still using CVS? Gosh what century are you living on.