Agreed! I’ve had to do a lot of this work myself since Mike Joyce challenged me to become a Git master ;) Challenge accepted.
But the more contributors can help to squash this stuff the better. Otherwise, my advice is —include and —exclude are your friends :) See #43 for how to use that. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Chief Architect Instrument Software and Science Data Systems Section (398) NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 168-519, Mailstop: 168-527 Email: [email protected] WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Associate Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -----Original Message----- From: Lewis John Mcgibbney <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Friday, July 3, 2015 at 9:29 AM To: "[email protected]" <[email protected]> Subject: Squashing Git Commits > > > >Hi Folks, >I would like to suggest that we developers and committers consider using >the squashing mechanism available and explained at the link below > >http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html > > > >It really helps with interpretation aspects of code review and also helps >improve the understating of provenance within Jira issues. > > >Thanks folks >Lewis > > >-- >Lewis >
