> > And I reiterate that I recall somewhere a suggestion on sage-devel > > that commit messages should be one line long. Does no one else > > remember that? Or did it mean it should not have any carriage > > returns, but be as long as it wants (in which case this was not clear > > at all)? > > Only the first line shows up by default so it should be self-contained > and concise (so that the listings are short). hg log -v will show long > commit messages, and hg log -p will print out the patches as well. >
Okay, this must be what I am remembering. In that case I say we should start asking officially in the developer's guide for long commit messages with short intros, and with a very explicit mention there that hg_sage.log(verbose=True) will give full info. I agree that the sage-combinat folks have nice long informative ones! I still like the redundancy, and see that as much less of an obstacle to developing than cryptic documents, but so be it. There remains one additional problem. If we have been putting long information into SPKG.txt for a while with almost no information in the commit messages, getting rid of the SPKG.txt ones will leave a fairly large piece of their history mysterious at best. Solutions? - kcrisman -- 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
