- 18 May, 2014 1 commit
-
-
The comment char is configurable and we need to provide a way for the user to specify which comment char they chose for their message.
Carlos Martín Nieto committed
-
- 27 Jan, 2014 1 commit
-
-
A lot of the tests were checking for overflow, which we don't have anymore, so we can remove them.
Carlos Martín Nieto committed
-
- 08 Jan, 2013 1 commit
-
-
Edward Thomson committed
-
- 23 Aug, 2012 1 commit
-
-
Russell Belfer committed
-
- 14 Aug, 2012 1 commit
-
-
If you want to be absolutely safe with git_message_prettify, you can now pass a NULL pointer for the buffer and get back the number of bytes that would be copied into the buffer. This means that an error is a non-negative return code and a success will be greater than zero from this function.
Russell Belfer committed
-
- 12 Aug, 2012 1 commit
-
-
This makes the message prettify buffer length check accurate.
Russell Belfer committed
-
- 19 Jun, 2012 1 commit
-
-
git_commit() and git_tag() no longer prettify the message by default. This has to be taken care of by the caller. This has the nice side effect of putting the caller in position to actually choose to strip the comments or not.
nulltoken committed
-
- 09 May, 2012 1 commit
-
-
Locale-aware bullshit bitting my ass again yo
Vicent Martí committed
-
- 08 May, 2012 2 commits
-
-
Vicent Martí committed
-
Vicent Martí committed
-
- 07 May, 2012 1 commit
-
-
'git commit' and 'git tag -a' enforce some conventions, like cleaning up excess whitespace and making sure that the last line ends with a '\n'. This fix replicates this behavior. Fix libgit2/libgit2sharp#117
nulltoken committed
-