Git fork
at reftables-rust 56 lines 2.1 kB view raw
1Git v2.36.2 Release Notes 2========================= 3 4This release merges up the fixes that appear in v2.30.5, v2.31.4, 5v2.32.3, v2.33.4, v2.34.4 and v2.35.4 to address the security 6issue CVE-2022-29187; see the release notes for these versions 7for details. 8 9Apart from that, this maintenance release is primarily to merge down 10updates to the build and CI procedures from the 'master' front, in 11order to ensure that we can cut healthy maintenance releases in the 12future. It also contains a handful of small and trivially-correct 13bugfixes. 14 15Fixes since v2.36.1 16------------------- 17 18 * Fixes real problems noticed by gcc 12 and works around false 19 positives. 20 21 * Update URL to the gitk repository. 22 23 * The "--current" option of "git show-branch" should have been made 24 incompatible with the "--reflog" mode, but this was not enforced, 25 which has been corrected. 26 27 * "git archive --add-file=<path>" picked up the raw permission bits 28 from the path and propagated to zip output in some cases, without 29 normalization, which has been corrected (tar output did not have 30 this issue). 31 32 * A bit of test framework fixes with a few fixes to issues found by 33 valgrind. 34 35 * macOS CI jobs have been occasionally flaky due to tentative version 36 skew between perforce and the homebrew packager. Instead of 37 failing the whole CI job, just let it skip the p4 tests when this 38 happens. 39 40 * The commit summary shown after making a commit is matched to what 41 is given in "git status" not to use the break-rewrite heuristics. 42 43 * Avoid problems from interaction between malloc_check and address 44 sanitizer. 45 46 * "git rebase --keep-base <upstream> <branch-to-rebase>" computed the 47 commit to rebase onto incorrectly, which has been corrected. 48 49 * The path taken by "git multi-pack-index" command from the end user 50 was compared with path internally prepared by the tool withut first 51 normalizing, which lead to duplicated paths not being noticed, 52 which has been corrected. 53 54 * "git clone --origin X" leaked piece of memory that held value read 55 from the clone.defaultRemoteName configuration variable, which has 56 been plugged.