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.
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| buffers.md | Loading commit data... | |
| changelog.md | Loading commit data... | |
| checkout-internals.md | Loading commit data... | |
| code_of_conduct.md | Loading commit data... | |
| coding-style.md | Loading commit data... | |
| contributing.md | Loading commit data... | |
| conventions.md | Loading commit data... | |
| diff-internals.md | Loading commit data... | |
| differences-from-git.md | Loading commit data... | |
| error-handling.md | Loading commit data... | |
| fuzzing.md | Loading commit data... | |
| merge-df_conflicts.txt | Loading commit data... | |
| projects.md | Loading commit data... | |
| release.md | Loading commit data... | |
| threading.md | Loading commit data... | |
| troubleshooting.md | Loading commit data... | |
| win32-longpaths.md | Loading commit data... |