> On 25 May 2010 20:58, Robert Bradshaw <rober...@math.washington.edu> wrote: > > On May 25, 2010, at 12:35 PM, kcrisman wrote: > >> SPKG.txt version > >> > >> === r-2.10.1.p0 (David Kirkby, February 16th 2010) === > > <Snip lots of stuff I wrote in an SPKG.txt file> > > >> Are you really suggesting that the commit message should be this > >> long? Maybe they should be! > > > > Yes, I've got no problem with long commit messages, the more info the > > better (especially for obscure build files and configure scripts, where > > the changes are far from self documenting). There are some nice commit > > messages in the combinat code too. > > If one is a Mercurial guru, then making long commit messages, changing > them when one makes a mistake, finding out what someone else has done > might all be pretty easy to you. > > But a simple text file is going to be a lot less intimidating for some > (many?).
I agree with that point of view. I have had lots of thoughts about the issue since the thread came up and my personal conclusion is that getting rid of simple text log will be a barrier to entry. It is fine to have a barrier for entry but you have to be sure that's what you want. Francois -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
