On Thu, 2006-12-07 at 14:42 +0100, Matthias Hopf wrote:
> On Dec 06, 06 13:16:26 -0500, Kristian Høgsberg wrote:
> > Another common mistake with the git commit message format.  There is a
> > convention that the first line in the commit message should be a
> > single short summary, optionally followed by a blank line and then a
> > more detailed description if you're so inclined:
> 
> It's actually not only a convention, git-rebase relies on that. It also
> enforces the blank line...

I believe that was considered a bug and fixed at some point. Rewriting
log messages is fairly harsh.

That they didn't notice it for so long is a strong indication of how
closely the kernel users follow the convention...

-- 
[EMAIL PROTECTED]

Attachment: signature.asc
Description: This is a digitally signed message part

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Mesa3d-dev mailing list
Mesa3d-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev

Reply via email to