| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
We used to hard-code the octothorpe as the comment character and the
documentation still mentions this even though we accept the comment character as
a parameter.
Update the line to indicate this and clean up the first paragraph a bit.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This is implemented in trailer.c and borrows a large amount of logic
from Git core to ensure compatibility.
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
A lot of the tests were checking for overflow, which we don't have
anymore, so we can remove them.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
|
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.
|