Project-Id-Version: Trac 0.12
Report-Msgid-Bugs-To: trac-dev@googlegroups.com
POT-Creation-Date: 2008-01-30 09:20+0100
PO-Revision-Date: 2010-07-19 23:05+0200
Last-Translator: Jeroen Ruigrok van der Werven <asmodai@in-nomine.org>
Language-Team: en_US <trac-dev@googlegroups.com>
Plural-Forms: nplurals=2; plural=(n != 1)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Generated-By: Babel 0.9.6

Warning: Can't synchronize with repository "(default)" (Unsupported version control system "git": Can't find an appropriate component, maybe the corresponding plugin was not enabled? ). Look in the Trac log for more information.

Changes between Version 6 and Version 7 of DevHelp


Ignore:
Timestamp:
01/02/13 08:11:20 (7 years ago)
Author:
sebastian
Comment:

Add commit message format

Legend:

Unmodified
Added
Removed
Modified
  • DevHelp

    v6 v7  
    1919 
    2020If you are not able to send a pull request send a patch file of your changes to support at phtagr.org via email. And if you are not able to send a patch file file you can send your complete file with changes to support at phtagr.org via email. 
     21 
     22== Git Commit Message == 
     23 
     24Commit messages should have following format (see [http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html A Note About Git Commit Messages] for details): 
     25 
     26{{{ 
     27Capitalized, short (50 chars or less) summary 
     28 
     29More detailed explanatory text, if necessary.  Wrap it to about 72 
     30characters or so.  In some contexts, the first line is treated as the 
     31subject of an email and the rest of the text as the body.  The blank 
     32line separating the summary from the body is critical (unless you omit 
     33the body entirely); tools like rebase can get confused if you run the 
     34two together. 
     35 
     36Write your commit message in the imperative: "Fix bug" and not "Fixed bug" 
     37or "Fixes bug."  This convention matches up with commit messages generated 
     38by commands like git merge and git revert. 
     39 
     40Further paragraphs come after blank lines. 
     41 
     42- Bullet points are okay, too 
     43 
     44- Typically a hyphen or asterisk is used for the bullet, preceded by a 
     45  single space, with blank lines in between, but conventions vary here 
     46 
     47- Use a hanging indent 
     48}}} 
    2149 
    2250= Source =