commit:     d74c5fd32ea8ff6ab1e79b8d746b2bba7d056978
Author:     Brian Dolbec <dolsen <AT> gentoo <DOT> org>
AuthorDate: Fri Apr  4 20:54:01 2014 +0000
Commit:     Brian Dolbec <brian.dolbec <AT> gmail <DOT> com>
CommitDate: Fri Apr  4 22:57:52 2014 +0000
URL:        
http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=d74c5fd3

DEVELOPING: 50 char limit for summary is too short

Upping it to 70, so with a file/module name prefix and
a bug postfix, there should be some space left for something intelligible.

---
 DEVELOPING | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/DEVELOPING b/DEVELOPING
index bcff318..0ffcbd7 100644
--- a/DEVELOPING
+++ b/DEVELOPING
@@ -179,7 +179,7 @@ Commit messages
 
 Commit messages should be in the imperative mood with a capitalised
 header, optionally followed by a newline and a more detailed explanatory
-text.  The headline should be capped at 50 characters, the detailed text
+text.  The headline should be capped at 70 characters, the detailed text
 at 72.  Prefix the message with the component you touched if this makes
 sense.  Postfix the message with the bug it fixes, if it does.  Example:
 

Reply via email to