[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Usefulness of Subject-header of git commit mails
From:       Andreas Hartmetz <ahartmetz () gmail ! com>
Date:       2011-01-28 16:42:35
Message-ID: 201101281742.35435.ahartmetz () gmail ! com
[Download RAW message or body]

On Monday 24 January 2011 00:13:26 Eike Hein wrote:
> 
> Yep - for the benefit of those who aren't used to the git
> jargon (sorry for that), in git the convention is to for-
> mat the commit message like this:
> 
> <single line of about 50 chars, followed optionally by:>
> <empty line>
> <longer message>
> 
> While deviating from this format is not particularly harm-
> ful, git and various tools based on git 'rely' on this
> convention to varying degrees.
> 
Semi-OT: What is the empty line good for?
Sometimes I just continue writing if the start of a long first sentence turns 
out to be a good summary.
[prev in list] [next in list] [prev in thread] [next in thread]