|
| 1 | +Git v2.46 Release Notes |
| 2 | +======================= |
| 3 | + |
| 4 | +Backward Compatibility Notes |
| 5 | + |
| 6 | + (None at this moment) |
| 7 | + |
| 8 | +UI, Workflows & Features |
| 9 | + |
| 10 | + * The "--rfc" option of "git format-patch" learned to take an |
| 11 | + optional string value to be used in place of "RFC" to tweak the |
| 12 | + "[PATCH]" on the subject header. |
| 13 | + (merge ce36894509 jc/format-patch-rfc-more later to maint). |
| 14 | + |
| 15 | + |
| 16 | +Performance, Internal Implementation, Development Support etc. |
| 17 | + |
| 18 | + * Advertise "git contacts", a tool for newcomers to find people to |
| 19 | + ask review for their patches, a bit more in our developer |
| 20 | + documentation. |
| 21 | + |
| 22 | + * In addition to building the objects needed, try to link the objects |
| 23 | + that are used in fuzzer tests, to make sure at least they build |
| 24 | + without bitrot, in Linux CI runs. |
| 25 | + |
| 26 | + |
| 27 | +Fixes since v2.45 |
| 28 | +----------------- |
| 29 | + |
| 30 | + * "git rebase --signoff" used to forget that it needs to add a |
| 31 | + sign-off to the resulting commit when told to continue after a |
| 32 | + conflict stops its operation. |
| 33 | + (merge a6c2654f83 pw/rebase-m-signoff-fix later to maint). |
| 34 | + |
| 35 | + * The procedure to build multi-pack-index got confused by the |
| 36 | + replace-refs mechanism, which has been corrected by disabling the |
| 37 | + latter. |
| 38 | + (merge 93e2ae1c95 xx/disable-replace-when-building-midx later to maint). |
| 39 | + |
| 40 | + * The "-k" and "--rfc" options of "format-patch" will now error out |
| 41 | + when used together, as one tells us not to add anything to the |
| 42 | + title of the commit, and the other one tells us to add "RFC" in |
| 43 | + addition to "PATCH". |
| 44 | + (merge cadcf58085 ds/format-patch-rfc-and-k later to maint). |
| 45 | + |
| 46 | + * "git stash -S" did not handle binary files correctly, which has |
| 47 | + been corrected. |
| 48 | + (merge 5fb7686409 aj/stash-staged-fix later to maint). |
| 49 | + |
| 50 | + * A scheduled "git maintenance" job is expected to work on all |
| 51 | + repositories it knows about, but it stopped at the first one that |
| 52 | + errored out. Now it keeps going. |
| 53 | + (merge c75662bfc9 js/for-each-repo-keep-going later to maint). |
| 54 | + |
| 55 | + * Other code cleanup, docfix, build fix, etc. |
0 commit comments