Finally got around to set up my branch properly.

[sdelmas]

This adds the Cassandra parser. Feel free to use it in any way you see fit. No copyright from my side, it's all yours.

[sukima]

Pull Requests are a lot easier to manage and merge if the commit messages are formatted well.

http://git-scm.com/book/ch5-2.html - has some good advise on commit messages.

Simply: the first line is your subject and is <= 50 characters. Then a blank line and finally the body of the commit message (72 characters long). Here is an example:

Short (50 chars or less) summary of changes

More detailed explanatory text, if necessary.  Wrap it to about 72
characters or so.  In some contexts, the first line is treated as the
subject of an email and the rest of the text as the body.  The blank
line separating the summary from the body is critical (unless you omit
the body entirely); tools like rebase can get confused if you run the
two together.

Further paragraphs come after blank lines.

 - Bullet points are okay, too

 - Typically a hyphen or asterisk is used for the bullet, preceded by a
   single space, with blank lines in between, but conventions vary here

Pull Requests are formated the same way only the 72 character width for the body should be ignored (GitHub manually places breaks in their markdown unlike normal markdown).