[prev in list] [next in list] [prev in thread] [next in thread]
List: leaf-devel
Subject: [leaf-devel] [Git] Good commit messages
From: Yves Blusseau <blusseau () users ! sourceforge ! net>
Date: 2012-08-28 13:10:20
Message-ID: 503CC33C.6050709 () users ! sourceforge ! net
[Download RAW message or body]
Hi all, it's very import to have good git commit messages.
The common use rule is to use a first short line (50 chars or less) that
is the summary for the commit.
Then a blank line
Then a more detailed explanatory text (wrap at about 72 chars). Use
paragraphs to separate topics.
If you use vim as your default editor with color syntax on, it will
colorize the first 50 chars of the first line, then wrap automaticaly
the third and above lines.
Please have a look at:
http://sethrobertson.github.com/GitBestPractices/#usemsg
and
http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
I know that this implies some efforts, but it will make our "life"
easier ( http://sethrobertson.github.com/GitBestPractices/#enforce ).
Yves
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic