Re: A word about Mercurial commit messages
Jeff Allen <[email protected]>
| Newsgroups | gmane.comp.lang.jython.devel |
|---|---|
| Message-ID | <[email protected]> |
I'm happy to follow Frank. Scrolling back down Hg Workbench I see that (lately) he, Indra and Santoso to varying degrees follow the recommended convention. (I'm not sure I can stick to 50 for the summary!) Hg Workbench gives me a settable red line, by default at column 80 (but 72 if we follow the blog). I seem to have wrap and EOL options, but they don't stick :(. Jeff Jeff Allen On 11/09/2014 23:47, Jim Baker wrote: > > +1, as a frequent violator myself. I plan to reform my ways ;), since > this makes a lot of sense for seeing the summaries in the abstract, vs > say just reviewing hg log. > > > -- > - Jim > Jim Baker > > > On September 11, 2014 at 3:44:06 PM, [email protected] > ([email protected] <mailto:[email protected]>) wrote: > >> On Thu, Sep 11, 2014 at 1:23 PM, Jeff Allen <[email protected]> wrote: >> > Mercurial will use your commit message up to the first line break >> as the >> > abstract it displays, for example here: http://hg.python.org/jython/ >> > Worth thinking about how that will read. I don't think we have an >> actual >> > rule about length. >> Although I don't always practice it, I like the guideline that I've >> seen in git circles detailed here: >> http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html >> >> The important part being a 50 char or less first line separated by a >> blank line, followed by the detailed message if necessary. >> >> -Frank >> >> ------------------------------------------------------------------------------ >> >> Want excitement? >> Manually upgrade your production database. >> When you want reliability, choose Perforce >> Perforce version control. Predictably reliable. >> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk >> >> _______________________________________________ >> Jython-dev mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/jython-dev ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ Jython-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jython-dev