summaryrefslogtreecommitdiffstats
path: root/Documentation/RelNotes
AgeCommit message (Collapse)AuthorLines
2022-08-10Git 2.37.2v2.37.2Junio C Hamano-0/+24
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-08-05Downmerge a bit more for 2.37.xJunio C Hamano-0/+17
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-07-27Downmerge a handful of fixes for 2.37.x maintenance trackJunio C Hamano-0/+47
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-07-04Git 2.37.1v2.37.1Junio C Hamano-0/+17
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-06-27Sync with Git 2.36.2Junio C Hamano-4/+53
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-06-23Git 2.36.2v2.36.2Johannes Schindelin-4/+10
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
2022-06-23Sync with 2.35.4Johannes Schindelin-0/+43
* maint-2.35: Git 2.35.4 Git 2.34.4 Git 2.33.4 Git 2.32.3 Git 2.31.4 Git 2.30.5 setup: tighten ownership checks post CVE-2022-24765 git-compat-util: allow root to access both SUDO_UID and root owned t0034: add negative tests and allow git init to mostly work under sudo git-compat-util: avoid failing dir ownership checks if running privileged t: regression git needs safe.directory when using sudo
2022-06-23Git 2.35.4v2.35.4Johannes Schindelin-0/+7
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
2022-06-23Sync with 2.34.4Johannes Schindelin-0/+36
* maint-2.34: Git 2.34.4 Git 2.33.4 Git 2.32.3 Git 2.31.4 Git 2.30.5 setup: tighten ownership checks post CVE-2022-24765 git-compat-util: allow root to access both SUDO_UID and root owned t0034: add negative tests and allow git init to mostly work under sudo git-compat-util: avoid failing dir ownership checks if running privileged t: regression git needs safe.directory when using sudo
2022-06-23Git 2.34.4v2.34.4Johannes Schindelin-0/+6
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
2022-06-23Sync with 2.33.4Johannes Schindelin-0/+30
* maint-2.33: Git 2.33.4 Git 2.32.3 Git 2.31.4 Git 2.30.5 setup: tighten ownership checks post CVE-2022-24765 git-compat-util: allow root to access both SUDO_UID and root owned t0034: add negative tests and allow git init to mostly work under sudo git-compat-util: avoid failing dir ownership checks if running privileged t: regression git needs safe.directory when using sudo
2022-06-23Git 2.33.4v2.33.4Johannes Schindelin-0/+6
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
2022-06-23Sync with 2.32.3Johannes Schindelin-0/+24
* maint-2.32: Git 2.32.3 Git 2.31.4 Git 2.30.5 setup: tighten ownership checks post CVE-2022-24765 git-compat-util: allow root to access both SUDO_UID and root owned t0034: add negative tests and allow git init to mostly work under sudo git-compat-util: avoid failing dir ownership checks if running privileged t: regression git needs safe.directory when using sudo
2022-06-23Git 2.32.3v2.32.3Johannes Schindelin-0/+6
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
2022-06-23Sync with 2.31.4Johannes Schindelin-0/+18
* maint-2.31: Git 2.31.4 Git 2.30.5 setup: tighten ownership checks post CVE-2022-24765 git-compat-util: allow root to access both SUDO_UID and root owned t0034: add negative tests and allow git init to mostly work under sudo git-compat-util: avoid failing dir ownership checks if running privileged t: regression git needs safe.directory when using sudo
2022-06-23Git 2.31.4v2.31.4Johannes Schindelin-0/+6
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
2022-06-23Sync with 2.30.5Johannes Schindelin-0/+12
* maint-2.30: Git 2.30.5 setup: tighten ownership checks post CVE-2022-24765 git-compat-util: allow root to access both SUDO_UID and root owned t0034: add negative tests and allow git init to mostly work under sudo git-compat-util: avoid failing dir ownership checks if running privileged t: regression git needs safe.directory when using sudo
2022-06-23Git 2.30.5v2.30.5Johannes Schindelin-0/+12
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
2022-06-17Git 2.37-rc1v2.37.0-rc1Junio C Hamano-3/+2
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-06-17Another batch of fixes before -rc1Junio C Hamano-1/+4
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-06-17Merge branch 'ab/credentials-in-url-more'Junio C Hamano-2/+4
Rename fetch.credentialsInUrl to transfer.credentialsInUrl as the single configuration variable should work both in pushing and fetching. * ab/credentials-in-url-more: transfer doc: move fetch.credentialsInUrl to "transfer" config namespace fetch doc: note "pushurl" caveat about "credentialsInUrl", elaborate
2022-06-15Fixes and updates post -rc0Junio C Hamano-5/+16
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-06-15transfer doc: move fetch.credentialsInUrl to "transfer" config namespaceÆvar Arnfjörð Bjarmason-1/+1
Rename the "fetch.credentialsInUrl" configuration variable introduced in 6dcbdc0d661 (remote: create fetch.credentialsInUrl config, 2022-06-06) to "transfer". There are existing exceptions, but generally speaking the "<namespace>.<var>" configuration should only apply to command described in the "namespace" (and its sub-commands, so e.g. "clone.*" or "fetch.*" might also configure "git-remote-https"). But in the case of "fetch.credentialsInUrl" we've got a configuration variable that configures the behavior of all of "clone", "push" and "fetch", someone adjusting "fetch.*" configuration won't expect to have the behavior of "git push" altered, especially as we have the pre-existing "{transfer,fetch,receive}.fsckObjects", which configures different parts of the transfer dialog. So let's move this configuration variable to the "transfer" namespace before it's exposed in a release. We could add all of "{transfer,fetch,pull}.credentialsInUrl" at some other time, but once we have "fetch" configure "pull" such an arrangement would would be a confusing mess, as we'd at least need to have "fetch" configure "push" (but not the other way around), or change existing behavior. Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com> Acked-by: Derrick Stolee <derrickstolee@github.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-06-15fetch doc: note "pushurl" caveat about "credentialsInUrl", elaborateÆvar Arnfjörð Bjarmason-1/+3
Amend the documentation and release notes entry for the "fetch.credentialsInUrl" feature added in 6dcbdc0d661 (remote: create fetch.credentialsInUrl config, 2022-06-06), it currently doesn't detect passwords in `remote.<name>.pushurl` configuration. We shouldn't lull users into a false sense of security, so we need to mention that prominently. This also elaborates and clarifies the "exposes the password in multiple ways" part of the documentation. As noted in [1] a user unfamiliar with git's implementation won't know what to make of that scary claim, e.g. git hypothetically have novel git-specific ways of exposing configured credentials. The reality is that this configuration is intended as an aid for users who can't fully trust their OS's or system's security model, so lets say that's what this is intended for, and mention the most common ways passwords stored in configuration might inadvertently get exposed. 1. https://lore.kernel.org/git/220524.86ilpuvcqh.gmgdl@evledraar.gmail.com/ Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com> Acked-by: Derrick Stolee <derrickstolee@github.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-06-13Git 2.37-rc0v2.37.0-rc0Junio C Hamano-0/+37
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-06-10Ninth batchJunio C Hamano-0/+18
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-06-08Sync with 'maint'Junio C Hamano-0/+50
2022-06-08Prepare for 2.36.2Junio C Hamano-0/+50
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-06-07Eighth batchJunio C Hamano-0/+13
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-06-03Seventh batchJunio C Hamano-0/+36
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-05-31Sixth batchJunio C Hamano-0/+5
Fast-tracking GitHub CI Windows build fixes. Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-05-30Fifth batchJunio C Hamano-0/+13
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-05-26Fourth batchJunio C Hamano-0/+19
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-05-25Third batchJunio C Hamano-0/+25
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-05-23Second batchJunio C Hamano-0/+10
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-05-20First batch for 2.37Junio C Hamano-0/+56
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-05-11second 0th batch of topics from the previous cycleJunio C Hamano-0/+16
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-05-100th batch for topics from the previous cycleJunio C Hamano-1/+22
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-05-05Sync with v2.36.1Junio C Hamano-0/+33
2022-05-05Git 2.36.1v2.36.1Junio C Hamano-0/+33
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-05-04A bit more regression fixes for 2.36Junio C Hamano-0/+34
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-04-28Some regression fixes for 2.36Junio C Hamano-0/+19
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-04-14Merge branch 'jc/revert-ref-transaction-hook-changes'Junio C Hamano-10/+0
Revert the "deletion of a ref should not trigger transaction events for loose and packed ref backends separately" that regresses the behaviour when a ref is not modified since it was packed. * jc/revert-ref-transaction-hook-changes: RelNotes: revert the description on the reverted topics Revert "fetch: increase test coverage of fetches" Revert "Merge branch 'ps/avoid-unnecessary-hook-invocation-with-packed-refs'"
2022-04-13RelNotes: revert the description on the reverted topicsJunio C Hamano-10/+0
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-04-13RelNotes: mention safe.directoryJunio C Hamano-2/+9
Helped-by: Philippe Blain <levraiphilippeblain@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-04-13RelNotes: clarify "bisect run unexecutable" tweakJunio C Hamano-4/+4
We do not have to guess how common the mistake the change targets is when describing it. Such an argument may be good while proposing a change, but does not quite belong in the record of what has already happened, i.e. a release note. Helped-by: Taylor Blau <me@ttaylorr.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-04-13Sync with Git 2.35.3Junio C Hamano-0/+41
2022-04-13Git 2.35.3v2.35.3Junio C Hamano-0/+41
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-04-13Git 2.34.3v2.34.3Junio C Hamano-0/+37
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-04-13Git 2.33.3v2.33.3Junio C Hamano-0/+33
Signed-off-by: Junio C Hamano <gitster@pobox.com>