On Thu, May 16, 2013 at 8:34 PM, Cyrille Artho <c.ar...@aist.go.jp> wrote: > Hi Scott, > IMHO many small commits are almost always a lot better. > > "git bisect" can be very useful in tracking down problems when you have many > small commits. With a single huge commit, that feature is almost useless. > > This benefit alone outweighs the small drawback of having multiple commit > messages. (If you used meaningful messages during your commits, they in > themselves can also be helpful.)
Thanks for your comments Cyrille. I committed the series here: 0d434033..43d71022 I'd still be interested in what others prefer for the future. Scott > > > Scott Kostyshak wrote: >> >> I'm about to commit a layout and template for the R Journal. I'm not >> sure whether I should make one commit or a series of commits. On the >> one hand, a series of commits gives more information about how the >> layout and template were developed and the commits document the >> decisions that were made. My thought is that for this case I will >> commit the series because I'm not confident in all of the decisions I >> made. This way it will be easier for someone who knows more about >> layouts to correct a poor decision I made (e.g. revert one of the >> commits). On the other hand, I'm not sure the advantages of multiple >> commits are worth the extra noise. >> >> Is there any convention for this for LyX development? If not, any >> personal opinions or advice? >> >> The commit history for this specific case can be viewed here: >> >> https://github.com/yihui/lyx/commits/master/layouts >> >> Scott >> > > -- > Regards, > Cyrille Artho - http://artho.com/ > They are ill discoverers that think there is no land, > when they can see nothing but sea. > -- Francis Bacon
