thodg/libgit2/src/message.c
Branch :
Log
| Author | Commit | Date | CI | Message |
|---|---|---|---|---|
 |
49e369b2 | 2014-05-18 10:06:49 | message: don't assume the comment char 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. | |
|
e1d7f003 | 2014-01-26 16:32:49 | messsage: use git_buf in prettify() A lot of the tests were checking for overflow, which we don't have anymore, so we can remove them. | |
 |
359fc2d2 | 2013-01-08 17:07:25 | update copyrights | |
 |
e9ca852e | 2012-08-23 09:20:17 | Fix warnings and merge issues on Win64 | |
|
85a0e28b | 2012-08-14 10:50:58 | Make git_message_prettify return bytes written 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. | |
|
fdc637c4 | 2012-08-12 09:08:45 | Check prettify message output buffer after cleanup This makes the message prettify buffer length check accurate. | |
 |
743a4b3b | 2012-06-15 22:24:59 | message: Expose git_message_prettify() 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. | |
 |
0f49200c | 2012-05-09 04:37:02 | msvc: Do not use `isspace` Locale-aware bullshit bitting my ass again yo | |
|
fd5faae3 | 2012-05-08 23:55:37 | message: Cleanup | |
|
b1e2ba27 | 2012-05-08 23:43:52 | message: Proper OOM handling | |
|
458b9450 | 2012-03-01 17:03:32 | commit/tag: ensure the message is cleaned up '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 |