summaryrefslogtreecommitdiff
path: root/tests/patch/parse.c
diff options
context:
space:
mode:
authorEdward Thomson <ethomson@edwardthomson.com>2021-09-23 21:16:36 -0400
committerEdward Thomson <ethomson@edwardthomson.com>2021-10-17 09:40:20 -0400
commit5346be3ddd3bcf19779c5d62e71f8442a0171133 (patch)
tree04e61288b4d517f94d48f6c003e14f81c9a1ef64 /tests/patch/parse.c
parent66ffac25110b3ab0f81e547f0045a1d0fe6991d5 (diff)
downloadlibgit2-5346be3ddd3bcf19779c5d62e71f8442a0171133.tar.gz
docs: document `git_buf`
We have been inconsistent about the way that we handle `git_buf`s provided by users. _Usually_ we require that it has been properly initialized with `GIT_BUF_INIT`, but _sometimes_ we simply overwrite the data in it regardless. And even more rarely, we will grow a user-provided buffer and concatenate data onto it (see `git_diff_format_email`). Document the path forward for `git_buf`, which is that we always require that the buffer is intitialized with `GIT_BUF_INIT`. `git_diff_format_email` will be kept backward compatible but users are encouraged to switch to the new `git_email` APIs.
Diffstat (limited to 'tests/patch/parse.c')
0 files changed, 0 insertions, 0 deletions