summaryrefslogtreecommitdiffstats
path: root/Documentation/RelNotes
AgeCommit message (Collapse)AuthorLines
2022-09-05The eighteenth batchJunio C Hamano-0/+17
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-09-01The seventeenth batchJunio C Hamano-1/+12
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-08-30Sync with Git 2.37.3Junio C Hamano-3/+3
2022-08-30Git 2.37.3v2.37.3Junio C Hamano-3/+3
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-08-29The sixteenth batchJunio C Hamano-21/+37
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-08-26Sync with 'maint'Junio C Hamano-0/+46
2022-08-26A handful more topics from the 'master' front for 2.37.3Junio C Hamano-0/+46
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-08-25The fifteenth batchJunio C Hamano-0/+16
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-08-18The fourteenth batchJunio C Hamano-0/+24
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-08-14The thirteenth batchJunio C Hamano-0/+12
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-08-12The twelfth batchJunio C Hamano-0/+4
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-08-10Sync with Git 2.37.2Junio C Hamano-11/+24
2022-08-10Git 2.37.2v2.37.2Junio C Hamano-0/+24
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-08-08The eleventh batchJunio C Hamano-0/+20
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-08-05The tenth batchJunio C Hamano-8/+11
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-08-05Sync with 'maint'Junio C Hamano-0/+17
2022-08-05Downmerge a bit more for 2.37.xJunio C Hamano-0/+17
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-08-03The ninth batchJunio C Hamano-0/+25
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-08-01The eighth batchJunio C Hamano-0/+16
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-07-27Sync with 'maint'Junio C Hamano-22/+47
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-27The seventh batchJunio C Hamano-0/+29
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-07-22The sixth batchJunio C Hamano-1/+16
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-07-19The fifth batchJunio C Hamano-0/+24
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-07-18The fourth batchJunio C Hamano-0/+34
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-07-14The third batchJunio C Hamano-2/+22
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-07-13The second batchJunio C Hamano-0/+35
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-07-11Sync with Git 2.37.1Junio C Hamano-4/+70
2022-07-11The first batch after Git 2.37Junio C Hamano-0/+31
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-07-02A regression fix for 2.37Junio C Hamano-0/+9
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>