diff options
| author | Johannes Schindelin <johannes.schindelin@gmx.de> | 2023-03-11 19:24:34 +0100 |
|---|---|---|
| committer | Johannes Schindelin <johannes.schindelin@gmx.de> | 2023-04-17 21:15:49 +0200 |
| commit | 31f7fe5e34612b4b8af3918d0b0cf2ea2545c2c4 (patch) | |
| tree | 84caab407ab446f3179892bb2a48bf4ff14ee295 /Documentation/RelNotes/2.31.8.txt | |
| parent | 2aedeff35fde779b03b57125b1f50f6c528bfbea (diff) | |
| parent | ea56f91275c1797776f10f4ac5d65671bb4f3e8b (diff) | |
| download | git-31f7fe5e34612b4b8af3918d0b0cf2ea2545c2c4.tar.xz | |
Sync with 2.31.8
* maint-2.31: (25 commits)
Git 2.31.8
tests: avoid using `test_i18ncmp`
Git 2.30.9
gettext: avoid using gettext if the locale dir is not present
apply --reject: overwrite existing `.rej` symlink if it exists
http.c: clear the 'finished' member once we are done with it
clone.c: avoid "exceeds maximum object size" error with GCC v12.x
range-diff: use ssize_t for parsed "len" in read_patches()
range-diff: handle unterminated lines in read_patches()
range-diff: drop useless "offset" variable from read_patches()
t5604: GETTEXT_POISON fix, conclusion
t5604: GETTEXT_POISON fix, part 1
t5619: GETTEXT_POISON fix
t0003: GETTEXT_POISON fix, conclusion
t0003: GETTEXT_POISON fix, part 1
t0033: GETTEXT_POISON fix
http: support CURLOPT_PROTOCOLS_STR
http: prefer CURLOPT_SEEKFUNCTION to CURLOPT_IOCTLFUNCTION
http-push: prefer CURLOPT_UPLOAD to CURLOPT_PUT
ci: install python on ubuntu
ci: use the same version of p4 on both Linux and macOS
...
Diffstat (limited to 'Documentation/RelNotes/2.31.8.txt')
| -rw-r--r-- | Documentation/RelNotes/2.31.8.txt | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/Documentation/RelNotes/2.31.8.txt b/Documentation/RelNotes/2.31.8.txt new file mode 100644 index 0000000000..0aa3080780 --- /dev/null +++ b/Documentation/RelNotes/2.31.8.txt @@ -0,0 +1,6 @@ +Git v2.31.8 Release Notes +========================= + +This release merges the fixes that appear in v2.30.9 to address the +security issues CVE-2023-25652, CVE-2023-25815, and CVE-2023-29007; +see the release notes for that version for details. |