Re: A word about Mercurial commit messages

"[email protected]" <[email protected]>
Newsgroups gmane.comp.lang.jython.devel
Message-ID <CADrh4zKvhd37chyUFiH-FhrAJTxf3EKJVB_WR0Qz_-_HacnAUA@mail.gmail.com>
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.