revert(3p/git): Revert merge of git upstream at v2.26.2
This causes cgit to serve error pages, which is undesirable. This reverts commit5229c9b232, reversing changes made tof2b211131f.
This commit is contained in:
Vincent Ambo
parent
6f8fbf4aa4
commit
93ba78d6f4
1006 changed files with 60537 additions and 148724 deletions
|
|
@ -251,7 +251,7 @@ Updates in v1.5.0 since v1.4.4 series
|
|||
the repository when that happens.
|
||||
|
||||
|
||||
* Cruft removal
|
||||
* Crufts removal
|
||||
|
||||
- We used to say "old commits are retrievable using reflog and
|
||||
'master@{yesterday}' syntax as long as you haven't run
|
||||
|
|
@ -379,7 +379,7 @@ Updates in v1.5.0 since v1.4.4 series
|
|||
- The value of i18n.commitencoding in the originating
|
||||
repository is recorded in the commit object on the "encoding"
|
||||
header, if it is not UTF-8. git-log and friends notice this,
|
||||
and re-encodes the message to the log output encoding when
|
||||
and reencodes the message to the log output encoding when
|
||||
displaying, if they are different. The log output encoding
|
||||
is determined by "git log --encoding=<encoding>",
|
||||
i18n.logoutputencoding configuration, or i18n.commitencoding
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ push running this release will issue a big warning when the
|
|||
configuration variable is missing. Please refer to:
|
||||
|
||||
http://git.or.cz/gitwiki/GitFaq#non-bare
|
||||
https://lore.kernel.org/git/7vbptlsuyv.fsf@gitster.siamese.dyndns.org/
|
||||
http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007
|
||||
|
||||
for more details on the reason why this change is needed and the
|
||||
transition plan.
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ push running this release will issue a big warning when the
|
|||
configuration variable is missing. Please refer to:
|
||||
|
||||
http://git.or.cz/gitwiki/GitFaq#non-bare
|
||||
https://lore.kernel.org/git/7vbptlsuyv.fsf@gitster.siamese.dyndns.org/
|
||||
http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007
|
||||
|
||||
for more details on the reason why this change is needed and the
|
||||
transition plan.
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ push running this release will issue a big warning when the
|
|||
configuration variable is missing. Please refer to:
|
||||
|
||||
http://git.or.cz/gitwiki/GitFaq#non-bare
|
||||
https://lore.kernel.org/git/7vbptlsuyv.fsf@gitster.siamese.dyndns.org/
|
||||
http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007
|
||||
|
||||
for more details on the reason why this change is needed and the
|
||||
transition plan.
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ Fixes since v1.6.5.3
|
|||
|
||||
* "git prune-packed" gave progress output even when its standard error is
|
||||
not connected to a terminal; this caused cron jobs that run it to
|
||||
produce cruft.
|
||||
produce crufts.
|
||||
|
||||
* "git pack-objects --all-progress" is an option to ask progress output
|
||||
from write-object phase _if_ progress output were to be produced, and
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ push running this release will issue a big warning when the
|
|||
configuration variable is missing. Please refer to:
|
||||
|
||||
http://git.or.cz/gitwiki/GitFaq#non-bare
|
||||
https://lore.kernel.org/git/7vbptlsuyv.fsf@gitster.siamese.dyndns.org/
|
||||
http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007
|
||||
|
||||
for more details on the reason why this change is needed and the
|
||||
transition plan.
|
||||
|
|
|
|||
|
|
@ -64,7 +64,7 @@ users will fare this time.
|
|||
Please refer to:
|
||||
|
||||
http://git.or.cz/gitwiki/GitFaq#non-bare
|
||||
https://lore.kernel.org/git/7vbptlsuyv.fsf@gitster.siamese.dyndns.org/
|
||||
http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007
|
||||
|
||||
for more details on the reason why this change is needed and the
|
||||
transition process that already took place so far.
|
||||
|
|
|
|||
|
|
@ -34,7 +34,7 @@ Fixes since v1.7.0.1
|
|||
* "git status" in 1.7.0 lacked the optimization we used to have in 1.6.X series
|
||||
to speed up scanning of large working tree.
|
||||
|
||||
* "gitweb" did not diagnose parsing errors properly while reading its configuration
|
||||
* "gitweb" did not diagnose parsing errors properly while reading tis configuration
|
||||
file.
|
||||
|
||||
And other minor fixes and documentation updates.
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ Fixes since v1.7.10.3
|
|||
* The message file for Swedish translation has been updated a bit.
|
||||
|
||||
* A name taken from mailmap was copied into an internal buffer
|
||||
incorrectly and could overrun the buffer if it is too long.
|
||||
incorrectly and could overun the buffer if it is too long.
|
||||
|
||||
* A malformed commit object that has a header line chomped in the
|
||||
middle could kill git with a NULL pointer dereference.
|
||||
|
|
|
|||
|
|
@ -25,7 +25,7 @@ Fixes since v1.7.12.2
|
|||
its Accept-Encoding header.
|
||||
|
||||
* "git receive-pack" (the counterpart to "git push") did not give
|
||||
progress output while processing objects it received to the user
|
||||
progress output while processing objects it received to the puser
|
||||
when run over the smart-http protocol.
|
||||
|
||||
* "git status" honored the ignore=dirty settings in .gitmodules but
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ Fixes since v1.7.5.2
|
|||
* "git log --stdin path" with an input that has additional pathspec
|
||||
used to corrupt memory.
|
||||
|
||||
* "git send-pack" (hence "git push") over smart-HTTP protocol could
|
||||
* "git send-pack" (hence "git push") over smalt-HTTP protocol could
|
||||
deadlock when the client side pack-object died early.
|
||||
|
||||
* Compressed tarball gitweb generates used to be made with the timestamp
|
||||
|
|
|
|||
|
|
@ -233,7 +233,7 @@ to them for details).
|
|||
together, misdetected branches.
|
||||
|
||||
* "git receive-pack" (the counterpart to "git push") did not give
|
||||
progress output while processing objects it received to the user
|
||||
progress output while processing objects it received to the puser
|
||||
when run over the smart-http protocol.
|
||||
|
||||
* When you misspell the command name you give to the "exec" action in
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ Fixes since v1.8.4
|
|||
in 1.8.4-rc1).
|
||||
|
||||
* "git rebase -i" and other scripted commands were feeding a
|
||||
random, data dependent error message to 'echo' and expecting it
|
||||
random, data dependant error message to 'echo' and expecting it
|
||||
to come out literally.
|
||||
|
||||
* Setting the "submodule.<name>.path" variable to the empty
|
||||
|
|
|
|||
|
|
@ -58,7 +58,7 @@ Foreign interfaces, subsystems and ports.
|
|||
credential helper interface from Git.pm.
|
||||
|
||||
* Update build for Cygwin 1.[57]. Torsten Bögershausen reports that
|
||||
this is fine with Cygwin 1.7 (cf. <51A606A0.5060101@web.de>) so let's try moving it
|
||||
this is fine with Cygwin 1.7 ($gmane/225824) so let's try moving it
|
||||
ahead.
|
||||
|
||||
* The credential helper to talk to keychain on OS X (in contrib/) has
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ Git v2.1.3 Release Notes
|
|||
they are new enough to support the `--output` option.
|
||||
|
||||
* "git pack-objects" forgot to disable the codepath to generate
|
||||
object reachability bitmap when it needs to split the resulting
|
||||
object recheability bitmap when it needs to split the resulting
|
||||
pack.
|
||||
|
||||
* "gitweb" used deprecated CGI::startfrom, which was removed from
|
||||
|
|
|
|||
|
|
@ -478,7 +478,7 @@ notes for details).
|
|||
* One part of "git am" had an oddball helper function that called
|
||||
stuff from outside "his" as opposed to calling what we have "ours",
|
||||
which was not gender-neutral and also inconsistent with the rest of
|
||||
the system where outside stuff is usually called "theirs" in
|
||||
the system where outside stuff is usuall called "theirs" in
|
||||
contrast to "ours".
|
||||
|
||||
* "git blame file" allowed the lineage of lines in the uncommitted,
|
||||
|
|
|
|||
|
|
@ -86,7 +86,7 @@ Fixes since v2.10.1
|
|||
by refusing to check out a branch that is already checked out in
|
||||
another worktree. However, this also prevented checking out a
|
||||
branch, which is designated as the primary branch of a bare
|
||||
repository, in a worktree that is connected to the bare
|
||||
reopsitory, in a worktree that is connected to the bare
|
||||
repository. The check has been corrected to allow it.
|
||||
|
||||
* "git rebase" immediately after "git clone" failed to find the fork
|
||||
|
|
|
|||
|
|
@ -104,7 +104,7 @@ Fixes since v2.11
|
|||
"git difftool --dir-diff" from a subdirectory never worked. This
|
||||
has been fixed.
|
||||
|
||||
* "git p4" that tracks multiple p4 paths imported a single changelist
|
||||
* "git p4" that tracks multile p4 paths imported a single changelist
|
||||
that touches files in these multiple paths as one commit, followed
|
||||
by many empty commits. This has been fixed.
|
||||
|
||||
|
|
|
|||
|
|
@ -315,7 +315,7 @@ notes for details).
|
|||
"git difftool --dir-diff" from a subdirectory never worked. This
|
||||
has been fixed.
|
||||
|
||||
* "git p4" that tracks multiple p4 paths imported a single changelist
|
||||
* "git p4" that tracks multile p4 paths imported a single changelist
|
||||
that touches files in these multiple paths as one commit, followed
|
||||
by many empty commits. This has been fixed.
|
||||
|
||||
|
|
|
|||
|
|
@ -177,7 +177,7 @@ UI, Workflows & Features
|
|||
been changed to enable "--decorate".
|
||||
|
||||
* The output from "git status --short" has been extended to show
|
||||
various kinds of dirtiness in submodules differently; instead of to
|
||||
various kinds of dirtyness in submodules differently; instead of to
|
||||
"M" for modified, 'm' and '?' can be shown to signal changes only
|
||||
to the working tree of the submodule but not the commit that is
|
||||
checked out.
|
||||
|
|
|
|||
|
|
@ -25,7 +25,7 @@ Fixes since v2.13.2
|
|||
* The code to pick up and execute command alias definition from the
|
||||
configuration used to switch to the top of the working tree and
|
||||
then come back when the expanded alias was executed, which was
|
||||
unnecessarily complex. Attempt to simplify the logic by using the
|
||||
unnecessarilyl complex. Attempt to simplify the logic by using the
|
||||
early-config mechanism that does not chdir around.
|
||||
|
||||
* "git add -p" were updated in 2.12 timeframe to cope with custom
|
||||
|
|
@ -35,7 +35,7 @@ Fixes since v2.13.2
|
|||
* Fix a recent regression to "git rebase -i" and add tests that would
|
||||
have caught it and others.
|
||||
|
||||
* An unaligned 32-bit access in pack-bitmap code has been corrected.
|
||||
* An unaligned 32-bit access in pack-bitmap code ahs been corrected.
|
||||
|
||||
* Tighten error checks for invalid "git apply" input.
|
||||
|
||||
|
|
|
|||
|
|
@ -141,7 +141,7 @@ Performance, Internal Implementation, Development Support etc.
|
|||
* Some platforms have ulong that is smaller than time_t, and our
|
||||
historical use of ulong for timestamp would mean they cannot
|
||||
represent some timestamp that the platform allows. Invent a
|
||||
separate and dedicated timestamp_t (so that we can distinguish
|
||||
separate and dedicated timestamp_t (so that we can distingiuish
|
||||
timestamps and a vanilla ulongs, which along is already a good
|
||||
move), and then declare uintmax_t is the type to be used as the
|
||||
timestamp_t.
|
||||
|
|
@ -442,7 +442,7 @@ notes for details).
|
|||
* The code to pick up and execute command alias definition from the
|
||||
configuration used to switch to the top of the working tree and
|
||||
then come back when the expanded alias was executed, which was
|
||||
unnecessarily complex. Attempt to simplify the logic by using the
|
||||
unnecessarilyl complex. Attempt to simplify the logic by using the
|
||||
early-config mechanism that does not chdir around.
|
||||
|
||||
* Fix configuration codepath to pay proper attention to commondir
|
||||
|
|
|
|||
|
|
@ -1,54 +0,0 @@
|
|||
Git v2.14.6 Release Notes
|
||||
=========================
|
||||
|
||||
This release addresses the security issues CVE-2019-1348,
|
||||
CVE-2019-1349, CVE-2019-1350, CVE-2019-1351, CVE-2019-1352,
|
||||
CVE-2019-1353, CVE-2019-1354, and CVE-2019-1387.
|
||||
|
||||
Fixes since v2.14.5
|
||||
-------------------
|
||||
|
||||
* CVE-2019-1348:
|
||||
The --export-marks option of git fast-import is exposed also via
|
||||
the in-stream command feature export-marks=... and it allows
|
||||
overwriting arbitrary paths.
|
||||
|
||||
* CVE-2019-1349:
|
||||
When submodules are cloned recursively, under certain circumstances
|
||||
Git could be fooled into using the same Git directory twice. We now
|
||||
require the directory to be empty.
|
||||
|
||||
* CVE-2019-1350:
|
||||
Incorrect quoting of command-line arguments allowed remote code
|
||||
execution during a recursive clone in conjunction with SSH URLs.
|
||||
|
||||
* CVE-2019-1351:
|
||||
While the only permitted drive letters for physical drives on
|
||||
Windows are letters of the US-English alphabet, this restriction
|
||||
does not apply to virtual drives assigned via subst <letter>:
|
||||
<path>. Git mistook such paths for relative paths, allowing writing
|
||||
outside of the worktree while cloning.
|
||||
|
||||
* CVE-2019-1352:
|
||||
Git was unaware of NTFS Alternate Data Streams, allowing files
|
||||
inside the .git/ directory to be overwritten during a clone.
|
||||
|
||||
* CVE-2019-1353:
|
||||
When running Git in the Windows Subsystem for Linux (also known as
|
||||
"WSL") while accessing a working directory on a regular Windows
|
||||
drive, none of the NTFS protections were active.
|
||||
|
||||
* CVE-2019-1354:
|
||||
Filenames on Linux/Unix can contain backslashes. On Windows,
|
||||
backslashes are directory separators. Git did not use to refuse to
|
||||
write out tracked files with such filenames.
|
||||
|
||||
* CVE-2019-1387:
|
||||
Recursive clones are currently affected by a vulnerability that is
|
||||
caused by too-lax validation of submodule names, allowing very
|
||||
targeted attacks via remote code execution in recursive clones.
|
||||
|
||||
Credit for finding these vulnerabilities goes to Microsoft Security
|
||||
Response Center, in particular to Nicolas Joly. The `fast-import`
|
||||
fixes were provided by Jeff King, the other fixes by Johannes
|
||||
Schindelin with help from Garima Singh.
|
||||
|
|
@ -1,11 +0,0 @@
|
|||
Git v2.15.4 Release Notes
|
||||
=========================
|
||||
|
||||
This release merges up the fixes that appear in v2.14.6 to address
|
||||
the security issues CVE-2019-1348, CVE-2019-1349, CVE-2019-1350,
|
||||
CVE-2019-1351, CVE-2019-1352, CVE-2019-1353, CVE-2019-1354, and
|
||||
CVE-2019-1387; see the release notes for that version for details.
|
||||
|
||||
In conjunction with a vulnerability that was fixed in v2.20.2,
|
||||
`.gitmodules` is no longer allowed to contain entries of the form
|
||||
`submodule.<name>.update=!command`.
|
||||
|
|
@ -407,7 +407,7 @@ Fixes since v2.15
|
|||
(merge eef3df5a93 bw/pathspec-match-submodule-boundary later to maint).
|
||||
|
||||
* Amending commits in git-gui broke the author name that is non-ascii
|
||||
due to incorrect encoding conversion.
|
||||
due to incorrect enconding conversion.
|
||||
|
||||
* Recent update to the submodule configuration code broke "diff-tree"
|
||||
by accidentally stopping to read from the index upfront.
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ Fixes since v2.16.2
|
|||
|
||||
* The http tracing code, often used to debug connection issues,
|
||||
learned to redact potentially sensitive information from its output
|
||||
so that it can be more safely shareable.
|
||||
so that it can be more safely sharable.
|
||||
|
||||
* Crash fix for a corner case where an error codepath tried to unlock
|
||||
what it did not acquire lock on.
|
||||
|
|
|
|||
|
|
@ -1,8 +0,0 @@
|
|||
Git v2.16.6 Release Notes
|
||||
=========================
|
||||
|
||||
This release merges up the fixes that appear in v2.14.6 and in
|
||||
v2.15.4 addressing the security issues CVE-2019-1348, CVE-2019-1349,
|
||||
CVE-2019-1350, CVE-2019-1351, CVE-2019-1352, CVE-2019-1353,
|
||||
CVE-2019-1354, and CVE-2019-1387; see the release notes for those
|
||||
versions for details.
|
||||
|
|
@ -216,7 +216,7 @@ Fixes since v2.16
|
|||
|
||||
* The http tracing code, often used to debug connection issues,
|
||||
learned to redact potentially sensitive information from its output
|
||||
so that it can be more safely shareable.
|
||||
so that it can be more safely sharable.
|
||||
(merge 8ba18e6fa4 jt/http-redact-cookies later to maint).
|
||||
|
||||
* Crash fix for a corner case where an error codepath tried to unlock
|
||||
|
|
|
|||
|
|
@ -1,12 +0,0 @@
|
|||
Git v2.17.3 Release Notes
|
||||
=========================
|
||||
|
||||
This release merges up the fixes that appear in v2.14.6 and in
|
||||
v2.15.4 addressing the security issues CVE-2019-1348, CVE-2019-1349,
|
||||
CVE-2019-1350, CVE-2019-1351, CVE-2019-1352, CVE-2019-1353,
|
||||
CVE-2019-1354, and CVE-2019-1387; see the release notes for those
|
||||
versions for details.
|
||||
|
||||
In addition, `git fsck` was taught to identify `.gitmodules` entries
|
||||
of the form `submodule.<name>.update=!command`, which have been
|
||||
disallowed in v2.15.4.
|
||||
|
|
@ -1,16 +0,0 @@
|
|||
Git v2.17.4 Release Notes
|
||||
=========================
|
||||
|
||||
This release is to address the security issue: CVE-2020-5260
|
||||
|
||||
Fixes since v2.17.3
|
||||
-------------------
|
||||
|
||||
* With a crafted URL that contains a newline in it, the credential
|
||||
helper machinery can be fooled to give credential information for
|
||||
a wrong host. The attack has been made impossible by forbidding
|
||||
a newline character in any value passed via the credential
|
||||
protocol.
|
||||
|
||||
Credit for finding the vulnerability goes to Felix Wilhelm of Google
|
||||
Project Zero.
|
||||
|
|
@ -1,22 +0,0 @@
|
|||
Git v2.17.5 Release Notes
|
||||
=========================
|
||||
|
||||
This release is to address a security issue: CVE-2020-11008
|
||||
|
||||
Fixes since v2.17.4
|
||||
-------------------
|
||||
|
||||
* With a crafted URL that contains a newline or empty host, or lacks
|
||||
a scheme, the credential helper machinery can be fooled into
|
||||
providing credential information that is not appropriate for the
|
||||
protocol in use and host being contacted.
|
||||
|
||||
Unlike the vulnerability CVE-2020-5260 fixed in v2.17.4, the
|
||||
credentials are not for a host of the attacker's choosing; instead,
|
||||
they are for some unspecified host (based on how the configured
|
||||
credential helper handles an absent "host" parameter).
|
||||
|
||||
The attack has been made impossible by refusing to work with
|
||||
under-specified credential patterns.
|
||||
|
||||
Credit for finding the vulnerability goes to Carlo Arenas.
|
||||
|
|
@ -179,7 +179,7 @@ Performance, Internal Implementation, Development Support etc.
|
|||
(merge 00a3da2a13 nd/remove-ignore-env-field later to maint).
|
||||
|
||||
* Code to find the length to uniquely abbreviate object names based
|
||||
on packfile content, which is a relatively recent addition, has been
|
||||
on packfile content, which is a relatively recent addtion, has been
|
||||
optimized to use the same fan-out table.
|
||||
|
||||
* The mechanism to use parse-options API to automate the command line
|
||||
|
|
|
|||
|
|
@ -1,8 +0,0 @@
|
|||
Git v2.18.2 Release Notes
|
||||
=========================
|
||||
|
||||
This release merges up the fixes that appear in v2.14.6, v2.15.4
|
||||
and in v2.17.3, addressing the security issues CVE-2019-1348,
|
||||
CVE-2019-1349, CVE-2019-1350, CVE-2019-1351, CVE-2019-1352,
|
||||
CVE-2019-1353, CVE-2019-1354, and CVE-2019-1387; see the release notes
|
||||
for those versions for details.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
Git v2.18.3 Release Notes
|
||||
=========================
|
||||
|
||||
This release merges the security fix that appears in v2.17.4; see
|
||||
the release notes for that version for details.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
Git v2.18.4 Release Notes
|
||||
=========================
|
||||
|
||||
This release merges the security fix that appears in v2.17.5; see
|
||||
the release notes for that version for details.
|
||||
|
|
@ -106,7 +106,7 @@ Performance, Internal Implementation, Development Support etc.
|
|||
* The conversion to pass "the_repository" and then "a_repository"
|
||||
throughout the object access API continues.
|
||||
|
||||
* Continuing with the idea to programmatically enumerate various
|
||||
* Continuing with the idea to programatically enumerate various
|
||||
pieces of data required for command line completion, teach the
|
||||
codebase to report the list of configuration variables
|
||||
subcommands care about to help complete them.
|
||||
|
|
|
|||
|
|
@ -1,8 +0,0 @@
|
|||
Git v2.19.3 Release Notes
|
||||
=========================
|
||||
|
||||
This release merges up the fixes that appear in v2.14.6, v2.15.4
|
||||
and in v2.17.3, addressing the security issues CVE-2019-1348,
|
||||
CVE-2019-1349, CVE-2019-1350, CVE-2019-1351, CVE-2019-1352,
|
||||
CVE-2019-1353, CVE-2019-1354, and CVE-2019-1387; see the release notes
|
||||
for those versions for details.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
Git v2.19.4 Release Notes
|
||||
=========================
|
||||
|
||||
This release merges the security fix that appears in v2.17.4; see
|
||||
the release notes for that version for details.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
Git v2.19.5 Release Notes
|
||||
=========================
|
||||
|
||||
This release merges the security fix that appears in v2.17.5; see
|
||||
the release notes for that version for details.
|
||||
|
|
@ -119,7 +119,7 @@ UI, Workflows & Features
|
|||
alias expansion.
|
||||
|
||||
* The documentation of "git gc" has been updated to mention that it
|
||||
is no longer limited to "pruning away cruft" but also updates
|
||||
is no longer limited to "pruning away crufts" but also updates
|
||||
ancillary files like commit-graph as a part of repository
|
||||
optimization.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,18 +0,0 @@
|
|||
Git v2.20.2 Release Notes
|
||||
=========================
|
||||
|
||||
This release merges up the fixes that appear in v2.14.6, v2.15.4
|
||||
and in v2.17.3, addressing the security issues CVE-2019-1348,
|
||||
CVE-2019-1349, CVE-2019-1350, CVE-2019-1351, CVE-2019-1352,
|
||||
CVE-2019-1353, CVE-2019-1354, and CVE-2019-1387; see the release notes
|
||||
for those versions for details.
|
||||
|
||||
The change to disallow `submodule.<name>.update=!command` entries in
|
||||
`.gitmodules` which was introduced v2.15.4 (and for which v2.17.3
|
||||
added explicit fsck checks) fixes the vulnerability in v2.20.x where a
|
||||
recursive clone followed by a submodule update could execute code
|
||||
contained within the repository without the user explicitly having
|
||||
asked for that (CVE-2019-19604).
|
||||
|
||||
Credit for finding this vulnerability goes to Joern Schneeweisz,
|
||||
credit for the fixes goes to Jonathan Nieder.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
Git v2.20.3 Release Notes
|
||||
=========================
|
||||
|
||||
This release merges the security fix that appears in v2.17.4; see
|
||||
the release notes for that version for details.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
Git v2.20.4 Release Notes
|
||||
=========================
|
||||
|
||||
This release merges the security fix that appears in v2.17.5; see
|
||||
the release notes for that version for details.
|
||||
|
|
@ -1,12 +0,0 @@
|
|||
Git v2.21.1 Release Notes
|
||||
=========================
|
||||
|
||||
This release merges up the fixes that appear in v2.14.6, v2.15.4,
|
||||
v2.17.3 and in v2.20.2, addressing the security issues CVE-2019-1348,
|
||||
CVE-2019-1349, CVE-2019-1350, CVE-2019-1351, CVE-2019-1352,
|
||||
CVE-2019-1353, CVE-2019-1354, CVE-2019-1387, and CVE-2019-19604;
|
||||
see the release notes for those versions for details.
|
||||
|
||||
Additionally, this version also includes a couple of fixes for the
|
||||
Windows-specific quoting of command-line arguments when Git executes
|
||||
a Unix shell on Windows.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
Git v2.21.2 Release Notes
|
||||
=========================
|
||||
|
||||
This release merges the security fix that appears in v2.17.4; see
|
||||
the release notes for that version for details.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
Git v2.21.3 Release Notes
|
||||
=========================
|
||||
|
||||
This release merges the security fix that appears in v2.17.5; see
|
||||
the release notes for that version for details.
|
||||
|
|
@ -1,8 +0,0 @@
|
|||
Git v2.22.2 Release Notes
|
||||
=========================
|
||||
|
||||
This release merges up the fixes that appear in v2.14.6, v2.15.4,
|
||||
v2.17.3, v2.20.2 and in v2.21.1, addressing the security issues
|
||||
CVE-2019-1348, CVE-2019-1349, CVE-2019-1350, CVE-2019-1351,
|
||||
CVE-2019-1352, CVE-2019-1353, CVE-2019-1354, CVE-2019-1387, and
|
||||
CVE-2019-19604; see the release notes for those versions for details.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
Git v2.22.3 Release Notes
|
||||
=========================
|
||||
|
||||
This release merges the security fix that appears in v2.17.4; see
|
||||
the release notes for that version for details.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
Git v2.22.4 Release Notes
|
||||
=========================
|
||||
|
||||
This release merges the security fix that appears in v2.17.5; see
|
||||
the release notes for that version for details.
|
||||
|
|
@ -1,8 +0,0 @@
|
|||
Git v2.23.1 Release Notes
|
||||
=========================
|
||||
|
||||
This release merges up the fixes that appear in v2.14.6, v2.15.4,
|
||||
v2.17.3, v2.20.2 and in v2.21.1, addressing the security issues
|
||||
CVE-2019-1348, CVE-2019-1349, CVE-2019-1350, CVE-2019-1351,
|
||||
CVE-2019-1352, CVE-2019-1353, CVE-2019-1354, CVE-2019-1387, and
|
||||
CVE-2019-19604; see the release notes for those versions for details.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
Git v2.23.2 Release Notes
|
||||
=========================
|
||||
|
||||
This release merges the security fix that appears in v2.17.4; see
|
||||
the release notes for that version for details.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
Git v2.23.3 Release Notes
|
||||
=========================
|
||||
|
||||
This release merges the security fix that appears in v2.17.5; see
|
||||
the release notes for that version for details.
|
||||
398
third_party/git/Documentation/RelNotes/2.24.0.txt
vendored
398
third_party/git/Documentation/RelNotes/2.24.0.txt
vendored
|
|
@ -1,398 +0,0 @@
|
|||
Git 2.24 Release Notes
|
||||
======================
|
||||
|
||||
Updates since v2.23
|
||||
-------------------
|
||||
|
||||
Backward compatibility note
|
||||
|
||||
* "filter-branch" is showing its age and alternatives are available.
|
||||
From this release, we started to discourage its use and hint
|
||||
people about filter-repo.
|
||||
|
||||
UI, Workflows & Features
|
||||
|
||||
* We now have an active interim maintainer for the Git-Gui part of
|
||||
the system. Praise and thank Pratyush Yadav for volunteering.
|
||||
|
||||
* The command line parser learned "--end-of-options" notation; the
|
||||
standard convention for scripters to have hardcoded set of options
|
||||
first on the command line, and force the command to treat end-user
|
||||
input as non-options, has been to use "--" as the delimiter, but
|
||||
that would not work for commands that use "--" as a delimiter
|
||||
between revs and pathspec.
|
||||
|
||||
* A mechanism to affect the default setting for a (related) group of
|
||||
configuration variables is introduced.
|
||||
|
||||
* "git fetch" learned "--set-upstream" option to help those who first
|
||||
clone from their private fork they intend to push to, add the true
|
||||
upstream via "git remote add" and then "git fetch" from it.
|
||||
|
||||
* Device-tree files learned their own userdiff patterns.
|
||||
(merge 3c81760bc6 sb/userdiff-dts later to maint).
|
||||
|
||||
* "git rebase --rebase-merges" learned to drive different merge
|
||||
strategies and pass strategy specific options to them.
|
||||
|
||||
* A new "pre-merge-commit" hook has been introduced.
|
||||
|
||||
* Command line completion updates for "git -c var.name=val" have been
|
||||
added.
|
||||
|
||||
* The lazy clone machinery has been taught that there can be more
|
||||
than one promisor remote and consult them in order when downloading
|
||||
missing objects on demand.
|
||||
|
||||
* The list-objects-filter API (used to create a sparse/lazy clone)
|
||||
learned to take a combined filter specification.
|
||||
|
||||
* The documentation and tests for "git format-patch" have been
|
||||
cleaned up.
|
||||
|
||||
* On Windows, the root level of UNC share is now allowed to be used
|
||||
just like any other directory.
|
||||
|
||||
* The command line completion support (in contrib/) learned about the
|
||||
"--skip" option of "git revert" and "git cherry-pick".
|
||||
|
||||
* "git rebase --keep-base <upstream>" tries to find the original base
|
||||
of the topic being rebased and rebase on top of that same base,
|
||||
which is useful when running the "git rebase -i" (and its limited
|
||||
variant "git rebase -x").
|
||||
|
||||
The command also has learned to fast-forward in more cases where it
|
||||
can instead of replaying to recreate identical commits.
|
||||
|
||||
* A configuration variable tells "git fetch" to write the commit
|
||||
graph after finishing.
|
||||
|
||||
* "git add -i" has been taught to show the total number of hunks and
|
||||
the hunks that has been processed so far when showing prompts.
|
||||
|
||||
* "git fetch --jobs=<n>" allowed <n> parallel jobs when fetching
|
||||
submodules, but this did not apply to "git fetch --multiple" that
|
||||
fetches from multiple remote repositories. It now does.
|
||||
|
||||
* The installation instruction for zsh completion script (in
|
||||
contrib/) has been a bit improved.
|
||||
|
||||
|
||||
Performance, Internal Implementation, Development Support etc.
|
||||
|
||||
* The code to write commit-graph over given commit object names has
|
||||
been made a bit more robust.
|
||||
|
||||
* The first line of verbose output from each test piece now carries
|
||||
the test name and number to help scanning with eyeballs.
|
||||
|
||||
* Further clean-up of the initialization code.
|
||||
|
||||
* xmalloc() used to have a mechanism to ditch memory and address
|
||||
space resources as the last resort upon seeing an allocation
|
||||
failure from the underlying malloc(), which made the code complex
|
||||
and thread-unsafe with dubious benefit, as major memory resource
|
||||
users already do limit their uses with various other mechanisms.
|
||||
It has been simplified away.
|
||||
|
||||
* Unnecessary full-tree diff in "git log -L" machinery has been
|
||||
optimized away.
|
||||
|
||||
* The http transport lacked some optimization the native transports
|
||||
learned to avoid unnecessary ref advertisement, which has been
|
||||
corrected.
|
||||
|
||||
* Preparation for SHA-256 upgrade continues in the test department.
|
||||
(merge 0c37c41d13 bc/hash-independent-tests-part-5 later to maint).
|
||||
|
||||
* The memory ownership model of the "git fast-import" got
|
||||
straightened out.
|
||||
|
||||
* Output from trace2 subsystem is formatted more prettily now.
|
||||
|
||||
* The internal code originally invented for ".gitignore" processing
|
||||
got reshuffled and renamed to make it less tied to "excluding" and
|
||||
stress more that it is about "matching", as it has been reused for
|
||||
things like sparse checkout specification that want to check if a
|
||||
path is "included".
|
||||
|
||||
* "git stash" learned to write refreshed index back to disk.
|
||||
|
||||
* Coccinelle checks are done on more source files than before now.
|
||||
|
||||
* The cache-tree code has been taught to be less aggressive in
|
||||
attempting to see if a tree object it computed already exists in
|
||||
the repository.
|
||||
|
||||
* The code to parse and use the commit-graph file has been made more
|
||||
robust against corrupted input.
|
||||
|
||||
* The hg-to-git script (in contrib/) has been updated to work with
|
||||
Python 3.
|
||||
|
||||
* Update the way build artifacts in t/helper/ directory are ignored.
|
||||
|
||||
* Preparation for SHA-256 upgrade continues.
|
||||
|
||||
* "git log --graph" for an octopus merge is sometimes colored
|
||||
incorrectly, which is demonstrated and documented but not yet
|
||||
fixed.
|
||||
|
||||
* The trace2 output, when sending them to files in a designated
|
||||
directory, can populate the directory with too many files; a
|
||||
mechanism is introduced to set the maximum number of files and
|
||||
discard further logs when the maximum is reached.
|
||||
|
||||
* We have adopted a Code-of-conduct document.
|
||||
(merge 3f9ef874a7 jk/coc later to maint).
|
||||
|
||||
|
||||
Fixes since v2.23
|
||||
-----------------
|
||||
|
||||
* "git grep --recurse-submodules" that looks at the working tree
|
||||
files looked at the contents in the index in submodules, instead of
|
||||
files in the working tree.
|
||||
(merge 6a289d45c0 mt/grep-submodules-working-tree later to maint).
|
||||
|
||||
* Codepaths to walk tree objects have been audited for integer
|
||||
overflows and hardened.
|
||||
(merge 5aa02f9868 jk/tree-walk-overflow later to maint).
|
||||
|
||||
* "git pack-refs" can lose refs that are created while running, which
|
||||
is getting corrected.
|
||||
(merge a613d4f817 sc/pack-refs-deletion-racefix later to maint).
|
||||
|
||||
* "git checkout" and "git restore" to re-populate the index from a
|
||||
tree-ish (typically HEAD) did not work correctly for a path that
|
||||
was removed and then added again with the intent-to-add bit, when
|
||||
the corresponding working tree file was empty. This has been
|
||||
corrected.
|
||||
|
||||
* Compilation fix.
|
||||
(merge 70597e8386 rs/nedalloc-fixlets later to maint).
|
||||
|
||||
* "git gui" learned to call the clean-up procedure before exiting.
|
||||
(merge 0d88f3d2c5 py/git-gui-do-quit later to maint).
|
||||
|
||||
* We promoted the "indent heuristics" that decides where to split
|
||||
diff hunks from experimental to the default a few years ago, but
|
||||
some stale documentation still marked it as experimental, which has
|
||||
been corrected.
|
||||
(merge 64e5e1fba1 sg/diff-indent-heuristic-non-experimental later to maint).
|
||||
|
||||
* Fix a mismerge that happened in 2.22 timeframe.
|
||||
(merge acb7da05ac en/checkout-mismerge-fix later to maint).
|
||||
|
||||
* "git archive" recorded incorrect length in extended pax header in
|
||||
some corner cases, which has been corrected.
|
||||
(merge 71d41ff651 rs/pax-extended-header-length-fix later to maint).
|
||||
|
||||
* On-demand object fetching in lazy clone incorrectly tried to fetch
|
||||
commits from submodule projects, while still working in the
|
||||
superproject, which has been corrected.
|
||||
(merge a63694f523 jt/diff-lazy-fetch-submodule-fix later to maint).
|
||||
|
||||
* Prepare get_short_oid() codepath to be thread-safe.
|
||||
(merge 7cfcb16b0e rs/sort-oid-array-thread-safe later to maint).
|
||||
|
||||
* "for-each-ref" and friends that show refs did not protect themselves
|
||||
against ancient tags that did not record tagger names when asked to
|
||||
show "%(taggername)", which have been corrected.
|
||||
(merge 8b3f33ef11 mp/for-each-ref-missing-name-or-email later to maint).
|
||||
|
||||
* The "git am" based backend of "git rebase" ignored the result of
|
||||
updating ".gitattributes" done in one step when replaying
|
||||
subsequent steps.
|
||||
(merge 2c65d90f75 bc/reread-attributes-during-rebase later to maint).
|
||||
|
||||
* Tell cURL library to use the same malloc() implementation, with the
|
||||
xmalloc() wrapper, as the rest of the system, for consistency.
|
||||
(merge 93b980e58f cb/curl-use-xmalloc later to maint).
|
||||
|
||||
* Build fix to adjust .gitignore to unignore a path that we started to track.
|
||||
(merge aac6ff7b5b js/visual-studio later to maint).
|
||||
|
||||
* A few implementation fixes in the notes API.
|
||||
(merge 60fe477a0b mh/notes-duplicate-entries later to maint).
|
||||
|
||||
* Fix an earlier regression to "git push --all" which should have
|
||||
been forbidden when the target remote repository is set to be a
|
||||
mirror.
|
||||
(merge 8e4c8af058 tg/push-all-in-mirror-forbidden later to maint).
|
||||
|
||||
* Fix an earlier regression in the test suite, which mistakenly
|
||||
stopped running HTTPD tests.
|
||||
(merge 3960290675 sg/git-test-boolean later to maint).
|
||||
|
||||
* "git rebase --autostash <upstream> <branch>", when <branch> is
|
||||
different from the current branch, incorrectly moved the tip of the
|
||||
current branch, which has been corrected.
|
||||
(merge bf1e28e0ad bw/rebase-autostash-keep-current-branch later to maint).
|
||||
|
||||
* Update support for Asciidoctor documentation toolchain.
|
||||
(merge 83b0b8953e ma/asciidoctor-refmiscinfo later to maint).
|
||||
|
||||
* Start using DocBook 5 (instead of DocBook 4.5) as Asciidoctor 2.0
|
||||
no longer works with the older one.
|
||||
(merge f6461b82b9 bc/doc-use-docbook-5 later to maint).
|
||||
|
||||
* The markup used in user-manual has been updated to work better with
|
||||
asciidoctor.
|
||||
(merge c4d2f6143a ma/user-manual-markup-update later to maint).
|
||||
|
||||
* Make sure the grep machinery does not abort when seeing a payload
|
||||
that is not UTF-8 even when JIT is not in use with PCRE1.
|
||||
(merge ad7c543e3b cb/skip-utf8-check-with-pcre1 later to maint).
|
||||
|
||||
* The name of the blob object that stores the filter specification
|
||||
for sparse cloning/fetching was interpreted in a wrong place in the
|
||||
code, causing Git to abort.
|
||||
|
||||
* "git log --decorate-refs-exclude=<pattern>" was incorrectly
|
||||
overruled when the "--simplify-by-decoration" option is used, which
|
||||
has been corrected.
|
||||
(merge 0cc7380d88 rs/simplify-by-deco-with-deco-refs-exclude later to maint).
|
||||
|
||||
* The "upload-pack" (the counterpart of "git fetch") needs to disable
|
||||
commit-graph when responding to a shallow clone/fetch request, but
|
||||
the way this was done made Git panic, which has been corrected.
|
||||
|
||||
* The object traversal machinery has been optimized not to load tree
|
||||
objects when we are only interested in commit history.
|
||||
(merge 72ed80c784 jk/list-objects-optim-wo-trees later to maint).
|
||||
|
||||
* The object name parser for "Nth parent" syntax has been made more
|
||||
robust against integer overflows.
|
||||
(merge 59fa5f5a25 rs/nth-parent-parse later to maint).
|
||||
|
||||
* The code used in following tags in "git fetch" has been optimized.
|
||||
(merge b7e2d8bca5 ms/fetch-follow-tag-optim later to maint).
|
||||
|
||||
* Regression fix for progress output.
|
||||
(merge 2bb74b53a4 sg/progress-fix later to maint).
|
||||
|
||||
* A bug in merge-recursive code that triggers when a branch with a
|
||||
symbolic link is merged with a branch that replaces it with a
|
||||
directory has been fixed.
|
||||
(merge 83e3ad3b12 jt/merge-recursive-symlink-is-not-a-dir-in-way later to maint).
|
||||
|
||||
* The rename detection logic sorts a list of rename source candidates
|
||||
by similarity to pick the best candidate, which means that a tie
|
||||
between sources with the same similarity is broken by the original
|
||||
location in the original candidate list (which is sorted by path).
|
||||
Force the sorting by similarity done with a stable sort, which is
|
||||
not promised by system supplied qsort(3), to ensure consistent
|
||||
results across platforms.
|
||||
(merge 2049b8dc65 js/diff-rename-force-stable-sort later to maint).
|
||||
|
||||
* The code to skip "UTF" and "UTF-" prefix, when computing an advice
|
||||
message, did not work correctly when the prefix was "UTF", which
|
||||
has been fixed.
|
||||
(merge b181676ce9 rs/convert-fix-utf-without-dash later to maint).
|
||||
|
||||
* The author names taken from SVN repositories may have extra leading
|
||||
or trailing whitespaces, which are now munged away.
|
||||
(merge 4ddd4bddb1 tk/git-svn-trim-author-name later to maint).
|
||||
|
||||
* "git rebase -i" showed a wrong HEAD while "reword" open the editor.
|
||||
(merge b0a3186140 pw/rebase-i-show-HEAD-to-reword later to maint).
|
||||
|
||||
* A few simplification and bugfixes to PCRE interface.
|
||||
(merge c581e4a749 ab/pcre-jit-fixes later to maint).
|
||||
|
||||
* PCRE fixes.
|
||||
(merge ff61681b46 cb/pcre1-cleanup later to maint).
|
||||
|
||||
* "git range-diff" segfaulted when diff.noprefix configuration was
|
||||
used, as it blindly expected the patch it internally generates to
|
||||
have the standard a/ and b/ prefixes. The command now forces the
|
||||
internal patch to be built without any prefix, not to be affected
|
||||
by any end-user configuration.
|
||||
(merge 937b76ed49 js/range-diff-noprefix later to maint).
|
||||
|
||||
* "git stash apply" in a subdirectory of a secondary worktree failed
|
||||
to access the worktree correctly, which has been corrected.
|
||||
(merge dfd557c978 js/stash-apply-in-secondary-worktree later to maint).
|
||||
|
||||
* The merge-recursive machinery is one of the most complex parts of
|
||||
the system that accumulated cruft over time. This large series
|
||||
cleans up the implementation quite a bit.
|
||||
(merge b657047719 en/merge-recursive-cleanup later to maint).
|
||||
|
||||
* Pretty-printed command line formatter (used in e.g. reporting the
|
||||
command being run by the tracing API) had a bug that lost an
|
||||
argument that is an empty string, which has been corrected.
|
||||
(merge ce2d7ed2fd gs/sq-quote-buf-pretty later to maint).
|
||||
|
||||
* "git range-diff" failed to handle mode-only change, which has been
|
||||
corrected.
|
||||
(merge 2b6a9b13ca tg/range-diff-output-update later to maint).
|
||||
|
||||
* Dev support update.
|
||||
(merge 4f3c1dc5d6 dl/allow-running-cocci-verbosely later to maint).
|
||||
|
||||
* "git format-patch -o <outdir>" did an equivalent of "mkdir <outdir>"
|
||||
not "mkdir -p <outdir>", which was corrected.
|
||||
|
||||
* "git stash save" lost local changes to submodules, which has been
|
||||
corrected.
|
||||
(merge 556895d0c8 jj/stash-reset-only-toplevel later to maint).
|
||||
|
||||
* The atomic push over smart HTTP transport did not work, which has
|
||||
been corrected.
|
||||
(merge 6f1194246a bc/smart-http-atomic-push later to maint).
|
||||
|
||||
* Other code cleanup, docfix, build fix, etc.
|
||||
(merge d1387d3895 en/fast-import-merge-doc later to maint).
|
||||
(merge 1c24a54ea4 bm/repository-layout-typofix later to maint).
|
||||
(merge 415b770b88 ds/midx-expire-repack later to maint).
|
||||
(merge 19800bdc3f nd/diff-parseopt later to maint).
|
||||
(merge 58166c2e9d tg/t0021-racefix later to maint).
|
||||
(merge 7027f508c7 dl/compat-cleanup later to maint).
|
||||
(merge e770fbfeff jc/test-cleanup later to maint).
|
||||
(merge 1fd881d404 rs/trace2-dst-warning later to maint).
|
||||
(merge 7e92756751 mh/http-urlmatch-cleanup later to maint).
|
||||
(merge 9784f97321 mh/release-commit-memory-fix later to maint).
|
||||
(merge 60d198d022 tb/banned-vsprintf-namefix later to maint).
|
||||
(merge 80e3658647 rs/help-unknown-ref-does-not-return later to maint).
|
||||
(merge 0a8bc7068f dt/remote-helper-doc-re-lock-option later to maint).
|
||||
(merge 27fd1e4ea7 en/merge-options-ff-and-friends later to maint).
|
||||
(merge 502c386ff9 sg/clean-nested-repo-with-ignored later to maint).
|
||||
(merge 26e3d1cbea am/mailmap-andrey-mazo later to maint).
|
||||
(merge 47b27c96fa ss/get-time-cleanup later to maint).
|
||||
(merge dd2e50a84e jk/commit-graph-cleanup later to maint).
|
||||
(merge 4fd39c76e6 cs/pretty-formats-doc-typofix later to maint).
|
||||
(merge 40e747e89d dl/submodule-set-branch later to maint).
|
||||
(merge 689a146c91 rs/commit-graph-use-list-count later to maint).
|
||||
(merge 0eb7c37a8a js/doc-patch-text later to maint).
|
||||
(merge 4b3aa170d1 rs/nth-switch-code-simplification later to maint).
|
||||
(merge 0d4304c124 ah/doc-submodule-ignore-submodules later to maint).
|
||||
(merge af78249463 cc/svn-fe-py-shebang later to maint).
|
||||
(merge 7bd97d6dff rs/alias-use-copy-array later to maint).
|
||||
(merge c46ebc2496 sg/travis-help-debug later to maint).
|
||||
(merge 24c681794f ps/my-first-contribution-alphasort later to maint).
|
||||
(merge 75b2c15435 cb/do-not-use-test-cmp-with-a later to maint).
|
||||
(merge cda0d497e3 bw/submodule-helper-usage-fix later to maint).
|
||||
(merge fe0ed5d5e9 am/visual-studio-config-fix later to maint).
|
||||
(merge 2e09c01232 sg/name-rev-cutoff-underflow-fix later to maint).
|
||||
(merge ddb3c856f3 as/shallow-slab-use-fix later to maint).
|
||||
(merge 71f4960b91 js/mingw-spawn-with-spaces-in-path later to maint).
|
||||
(merge 53d687bf5f ah/cleanups later to maint).
|
||||
(merge f537485fa5 rs/test-remove-useless-debugging-cat later to maint).
|
||||
(merge 11a3d3aadd dl/rev-list-doc-cleanup later to maint).
|
||||
(merge d928a8388a am/t0028-utf16-tests later to maint).
|
||||
(merge b05b40930e dl/t0000-skip-test-test later to maint).
|
||||
(merge 03d3b1297c js/xdiffi-comment-updates later to maint).
|
||||
(merge 57d8f4b4c7 js/doc-stash-save later to maint).
|
||||
(merge 8c1cfd58e3 ta/t1308-typofix later to maint).
|
||||
(merge fa364ad790 bb/utf8-wcwidth-cleanup later to maint).
|
||||
(merge 68b69211b2 bb/compat-util-comment-fix later to maint).
|
||||
(merge 5cc6a4be11 rs/http-push-simplify later to maint).
|
||||
(merge a81e42d235 rs/column-use-utf8-strnwidth later to maint).
|
||||
(merge 062a309d36 rs/remote-curl-use-argv-array later to maint).
|
||||
(merge 3b3c79f6c9 nr/diff-highlight-indent-fix later to maint).
|
||||
(merge 3444ec2eb2 wb/fsmonitor-bitmap-fix later to maint).
|
||||
(merge 10da030ab7 cb/pcre2-chartables-leakfix later to maint).
|
||||
(merge 60e6569a12 js/mingw-needs-hiding-fix later to maint).
|
||||
(merge 52bd3e4657 rl/gitweb-blame-prev-fix later to maint).
|
||||
|
|
@ -1,8 +0,0 @@
|
|||
Git v2.24.1 Release Notes
|
||||
=========================
|
||||
|
||||
This release merges up the fixes that appear in v2.14.6, v2.15.4,
|
||||
v2.17.3, v2.20.2 and in v2.21.1, addressing the security issues
|
||||
CVE-2019-1348, CVE-2019-1349, CVE-2019-1350, CVE-2019-1351,
|
||||
CVE-2019-1352, CVE-2019-1353, CVE-2019-1354, CVE-2019-1387, and
|
||||
CVE-2019-19604; see the release notes for those versions for details.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
Git v2.24.2 Release Notes
|
||||
=========================
|
||||
|
||||
This release merges the security fix that appears in v2.17.4; see
|
||||
the release notes for that version for details.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
Git v2.24.3 Release Notes
|
||||
=========================
|
||||
|
||||
This release merges the security fix that appears in v2.17.5; see
|
||||
the release notes for that version for details.
|
||||
370
third_party/git/Documentation/RelNotes/2.25.0.txt
vendored
370
third_party/git/Documentation/RelNotes/2.25.0.txt
vendored
|
|
@ -1,370 +0,0 @@
|
|||
Git 2.25 Release Notes
|
||||
======================
|
||||
|
||||
Updates since v2.24
|
||||
-------------------
|
||||
|
||||
Backward compatibility notes
|
||||
|
||||
|
||||
UI, Workflows & Features
|
||||
|
||||
* A tutorial on object enumeration has been added.
|
||||
|
||||
* The branch description ("git branch --edit-description") has been
|
||||
used to fill the body of the cover letters by the format-patch
|
||||
command; this has been enhanced so that the subject can also be
|
||||
filled.
|
||||
|
||||
* "git rebase --preserve-merges" has been marked as deprecated; this
|
||||
release stops advertising it in the "git rebase -h" output.
|
||||
|
||||
* The code to generate multi-pack index learned to show (or not to
|
||||
show) progress indicators.
|
||||
|
||||
* "git apply --3way" learned to honor merge.conflictStyle
|
||||
configuration variable, like merges would.
|
||||
|
||||
* The custom format for "git log --format=<format>" learned the l/L
|
||||
placeholder that is similar to e/E that fills in the e-mail
|
||||
address, but only the local part on the left side of '@'.
|
||||
|
||||
* Documentation pages for "git shortlog" now list commit limiting
|
||||
options explicitly.
|
||||
|
||||
* The patterns to detect function boundary for Elixir language has
|
||||
been added.
|
||||
|
||||
* The completion script (in contrib/) learned that the "--onto"
|
||||
option of "git rebase" can take its argument as the value of the
|
||||
option.
|
||||
|
||||
* The userdiff machinery has been taught that "async def" is another
|
||||
way to begin a "function" in Python.
|
||||
|
||||
* "git range-diff" learned to take the "--notes=<ref>" and the
|
||||
"--no-notes" options to control the commit notes included in the
|
||||
log message that gets compared.
|
||||
|
||||
* "git rev-parse --show-toplevel" run outside of any working tree did
|
||||
not error out, which has been corrected.
|
||||
|
||||
* A few commands learned to take the pathspec from the standard input
|
||||
or a named file, instead of taking it as the command line
|
||||
arguments, with the "--pathspec-from-file" option.
|
||||
|
||||
* "git submodule" learned a subcommand "set-url".
|
||||
|
||||
* "git log" family learned "--pretty=reference" that gives the name
|
||||
of a commit in the format that is often used to refer to it in log
|
||||
messages.
|
||||
|
||||
* The interaction between "git clone --recurse-submodules" and
|
||||
alternate object store was ill-designed. The documentation and
|
||||
code have been taught to make more clear recommendations when the
|
||||
users see failures.
|
||||
|
||||
* Management of sparsely checked-out working tree has gained a
|
||||
dedicated "sparse-checkout" command.
|
||||
|
||||
* Miscellaneous small UX improvements on "git-p4".
|
||||
|
||||
* "git sparse-checkout list" subcommand learned to give its output in
|
||||
a more concise form when the "cone" mode is in effect.
|
||||
|
||||
|
||||
Performance, Internal Implementation, Development Support etc.
|
||||
|
||||
* Debugging support for lazy cloning has been a bit improved.
|
||||
|
||||
* Move the definition of a set of bitmask constants from 0ctal
|
||||
literal to (1U<<count) notation.
|
||||
|
||||
* Test updates to prepare for SHA-2 transition continues.
|
||||
|
||||
* Crufty code and logic accumulated over time around the object
|
||||
parsing and low-level object access used in "git fsck" have been
|
||||
cleaned up.
|
||||
|
||||
* The implementation of "git log --graph" got refactored and then its
|
||||
output got simplified.
|
||||
|
||||
* Follow recent push to move API docs from Documentation/ to header
|
||||
files and update config.h
|
||||
|
||||
* "git bundle" has been taught to use the parse options API. "git
|
||||
bundle verify" learned "--quiet" and "git bundle create" learned
|
||||
options to control the progress output.
|
||||
|
||||
* Handling of commit objects that use non UTF-8 encoding during
|
||||
"rebase -i" has been improved.
|
||||
|
||||
* The beginning of rewriting "git add -i" in C.
|
||||
|
||||
* A label used in the todo list that are generated by "git rebase
|
||||
--rebase-merges" is used as a part of a refname; the logic to come
|
||||
up with the label has been tightened to avoid names that cannot be
|
||||
used as such.
|
||||
|
||||
* The logic to avoid duplicate label names generated by "git rebase
|
||||
--rebase-merges" forgot that the machinery itself uses "onto" as a
|
||||
label name, which must be avoided by auto-generated labels, which
|
||||
has been corrected.
|
||||
|
||||
* We have had compatibility fallback macro definitions for "PRIuMAX",
|
||||
"PRIu32", etc. but did not for "PRIdMAX", while the code used the
|
||||
last one apparently without any hiccup reported recently. The
|
||||
fallback macro definitions for these <inttypes.h> macros that must
|
||||
appear in C99 systems have been removed.
|
||||
|
||||
* Recently we have declared that GIT_TEST_* variables take the
|
||||
usual boolean values (it used to be that some used "non-empty
|
||||
means true" and taking GIT_TEST_VAR=YesPlease as true); make
|
||||
sure we notice and fail when non-bool strings are given to
|
||||
these variables.
|
||||
|
||||
* Users of oneway_merge() (like "reset --hard") learned to take
|
||||
advantage of fsmonitor to avoid unnecessary lstat(2) calls.
|
||||
|
||||
* Performance tweak on "git push" into a repository with many refs
|
||||
that point at objects we have never heard of.
|
||||
|
||||
* PerfTest fix to avoid stale result mixed up with the latest round
|
||||
of test results.
|
||||
|
||||
* Hide lower-level verify_signed-buffer() API as a pure helper to
|
||||
implement the public check_signature() function, in order to
|
||||
encourage new callers to use the correct and more strict
|
||||
validation.
|
||||
|
||||
* Unnecessary reading of state variables back from the disk during
|
||||
sequencer operation has been reduced.
|
||||
|
||||
* The code has been made to avoid gmtime() and localtime() and prefer
|
||||
their reentrant counterparts.
|
||||
|
||||
* In a repository with many packfiles, the cost of the procedure that
|
||||
avoids registering the same packfile twice was unnecessarily high
|
||||
by using an inefficient search algorithm, which has been corrected.
|
||||
|
||||
* Redo "git name-rev" to avoid recursive calls.
|
||||
|
||||
* FreeBSD CI support via Cirrus-CI has been added.
|
||||
|
||||
|
||||
Fixes since v2.24
|
||||
-----------------
|
||||
|
||||
* "rebase -i" ceased to run post-commit hook by mistake in an earlier
|
||||
update, which has been corrected.
|
||||
|
||||
* "git notes copy $original" ought to copy the notes attached to the
|
||||
original object to HEAD, but a mistaken tightening to command line
|
||||
parameter validation made earlier disabled that feature by mistake.
|
||||
|
||||
* When all files from some subdirectory were renamed to the root
|
||||
directory, the directory rename heuristics would fail to detect that
|
||||
as a rename/merge of the subdirectory to the root directory, which has
|
||||
been corrected.
|
||||
|
||||
* Code clean-up and a bugfix in the logic used to tell worktree local
|
||||
and repository global refs apart.
|
||||
(merge f45f88b2e4 sg/dir-trie-fixes later to maint).
|
||||
|
||||
* "git stash save" in a working tree that is sparsely checked out
|
||||
mistakenly removed paths that are outside the area of interest.
|
||||
(merge 4a58c3d7f7 js/update-index-ignore-removal-for-skip-worktree later to maint).
|
||||
|
||||
* "git rev-parse --git-path HEAD.lock" did not give the right path
|
||||
when run in a secondary worktree.
|
||||
(merge 76a53d640f js/git-path-head-dot-lock-fix later to maint).
|
||||
|
||||
* "git merge --no-commit" needs "--no-ff" if you do not want to move
|
||||
HEAD, which has been corrected in the manual page for "git bisect".
|
||||
(merge 8dd327b246 ma/bisect-doc-sample-update later to maint).
|
||||
|
||||
* "git worktree add" internally calls "reset --hard" that should not
|
||||
descend into submodules, even when submodule.recurse configuration
|
||||
is set, but it was affected. This has been corrected.
|
||||
(merge 4782cf2ab6 pb/no-recursive-reset-hard-in-worktree-add later to maint).
|
||||
|
||||
* Messages from die() etc. can be mixed up from multiple processes
|
||||
without even line buffering on Windows, which has been worked
|
||||
around.
|
||||
(merge 116d1fa6c6 js/vreportf-wo-buffering later to maint).
|
||||
|
||||
* HTTP transport had possible allocator/deallocator mismatch, which
|
||||
has been corrected.
|
||||
|
||||
* The watchman integration for fsmonitor was racy, which has been
|
||||
corrected to be more conservative.
|
||||
(merge dd0b61f577 kw/fsmonitor-watchman-fix later to maint).
|
||||
|
||||
* Fetching from multiple remotes into the same repository in parallel
|
||||
had a bad interaction with the recent change to (optionally) update
|
||||
the commit-graph after a fetch job finishes, as these parallel
|
||||
fetches compete with each other. Which has been corrected.
|
||||
|
||||
* Recent update to "git stash pop" made the command empty the index
|
||||
when run with the "--quiet" option, which has been corrected.
|
||||
|
||||
* "git fetch" codepath had a big "do not lazily fetch missing objects
|
||||
when I ask if something exists" switch. This has been corrected by
|
||||
marking the "does this thing exist?" calls with "if not please do not
|
||||
lazily fetch it" flag.
|
||||
|
||||
* Test update to avoid wasted cycles.
|
||||
(merge e0316695ec sg/skip-skipped-prereq later to maint).
|
||||
|
||||
* Error handling after "git push" finishes sending the packdata and
|
||||
waits for the response to the remote side has been improved.
|
||||
(merge ad7a403268 jk/send-pack-remote-failure later to maint).
|
||||
|
||||
* Some codepaths in "gitweb" that forgot to escape URLs generated
|
||||
based on end-user input have been corrected.
|
||||
(merge a376e37b2c jk/gitweb-anti-xss later to maint).
|
||||
|
||||
* CI jobs for macOS has been made less chatty when updating perforce
|
||||
package used during testing.
|
||||
(merge 0dbc4a0edf jc/azure-ci-osx-fix-fix later to maint).
|
||||
|
||||
* "git unpack-objects" used to show progress based only on the number
|
||||
of received and unpacked objects, which stalled when it has to
|
||||
handle an unusually large object. It now shows the throughput as
|
||||
well.
|
||||
(merge bae60ba7e9 sg/unpack-progress-throughput later to maint).
|
||||
|
||||
* The sequencer machinery compared the HEAD and the state it is
|
||||
attempting to commit to decide if the result would be a no-op
|
||||
commit, even when amending a commit, which was incorrect, and
|
||||
has been corrected.
|
||||
|
||||
* The code to parse GPG output used to assume incorrectly that the
|
||||
finterprint for the primary key would always be present for a valid
|
||||
signature, which has been corrected.
|
||||
(merge 67a6ea6300 hi/gpg-optional-pkfp-fix later to maint).
|
||||
|
||||
* "git submodule status" and "git submodule status --cached" show
|
||||
different things, but the documentation did not cover them
|
||||
correctly, which has been corrected.
|
||||
(merge 8d483c8408 mg/doc-submodule-status-cached later to maint).
|
||||
|
||||
* "git reset --patch $object" without any pathspec should allow a
|
||||
tree object to be given, but incorrectly required a committish,
|
||||
which has been corrected.
|
||||
|
||||
* "git submodule status" that is run from a subdirectory of the
|
||||
superproject did not work well, which has been corrected.
|
||||
(merge 1f3aea22c7 mg/submodule-status-from-a-subdirectory later to maint).
|
||||
|
||||
* The revision walking machinery uses resources like per-object flag
|
||||
bits that need to be reset before a new iteration of walking
|
||||
begins, but the resources related to topological walk were not
|
||||
cleared correctly, which has been corrected.
|
||||
(merge 0aa0c2b2ec mh/clear-topo-walk-upon-reset later to maint).
|
||||
|
||||
* TravisCI update.
|
||||
(merge 176441bfb5 sg/osx-force-gcc-9 later to maint).
|
||||
|
||||
* While running "revert" or "cherry-pick --edit" for multiple
|
||||
commits, a recent regression incorrectly detected "nothing to
|
||||
commit, working tree clean", instead of replaying the commits,
|
||||
which has been corrected.
|
||||
(merge befd4f6a81 sg/assume-no-todo-update-in-cherry-pick later to maint).
|
||||
|
||||
* Work around a issue where a FD that is left open when spawning a
|
||||
child process and is kept open in the child can interfere with the
|
||||
operation in the parent process on Windows.
|
||||
|
||||
* One kind of progress messages were always given during commit-graph
|
||||
generation, instead of following the "if it takes more than two
|
||||
seconds, show progress" pattern, which has been corrected.
|
||||
|
||||
* "git rebase" did not work well when format.useAutoBase
|
||||
configuration variable is set, which has been corrected.
|
||||
|
||||
* The "diff" machinery learned not to lose added/removed blank lines
|
||||
in the context when --ignore-blank-lines and --function-context are
|
||||
used at the same time.
|
||||
(merge 0bb313a552 rs/xdiff-ignore-ws-w-func-context later to maint).
|
||||
|
||||
* The test on "fast-import" used to get stuck when "fast-import" died
|
||||
in the middle.
|
||||
(merge 0d9b0d7885 sg/t9300-robustify later to maint).
|
||||
|
||||
* "git format-patch" can take a set of configured format.notes values
|
||||
to specify which notes refs to use in the log message part of the
|
||||
output. The behaviour of this was not consistent with multiple
|
||||
--notes command line options, which has been corrected.
|
||||
(merge e0f9095aaa dl/format-patch-notes-config-fixup later to maint).
|
||||
|
||||
* "git p4" used to ignore lfs.storage configuration variable, which
|
||||
has been corrected.
|
||||
(merge ea94b16fb8 rb/p4-lfs later to maint).
|
||||
|
||||
* Assorted fixes to the directory traversal API.
|
||||
(merge 6836d2fe06 en/fill-directory-fixes later to maint).
|
||||
|
||||
* Forbid pathnames that the platform's filesystem cannot represent on
|
||||
MinGW.
|
||||
(merge 4dc42c6c18 js/mingw-reserved-filenames later to maint).
|
||||
|
||||
* "git rebase --signoff" stopped working when the command was written
|
||||
in C, which has been corrected.
|
||||
(merge 4fe7e43c53 en/rebase-signoff-fix later to maint).
|
||||
|
||||
* An earlier update to Git for Windows declared that a tree object is
|
||||
invalid if it has a path component with backslash in it, which was
|
||||
overly strict, which has been corrected. The only protection the
|
||||
Windows users need is to prevent such path (or any path that their
|
||||
filesystem cannot check out) from entering the index.
|
||||
(merge 224c7d70fa js/mingw-loosen-overstrict-tree-entry-checks later to maint).
|
||||
|
||||
* The code to write split commit-graph file(s) upon fetching computed
|
||||
bogus value for the parameter used in splitting the resulting
|
||||
files, which has been corrected.
|
||||
(merge 63020f175f ds/commit-graph-set-size-mult later to maint).
|
||||
|
||||
* Other code cleanup, docfix, build fix, etc.
|
||||
(merge 80736d7c5e jc/am-show-current-patch-docfix later to maint).
|
||||
(merge 8b656572ca sg/commit-graph-usage-fix later to maint).
|
||||
(merge 6c02042139 mr/clone-dir-exists-to-path-exists later to maint).
|
||||
(merge 44ae131e38 sg/blame-indent-heuristics-is-now-the-default later to maint).
|
||||
(merge 0115e5d929 dl/doc-diff-no-index-implies-exit-code later to maint).
|
||||
(merge 270de6acbe en/t6024-style later to maint).
|
||||
(merge 14c4776d75 ns/test-desc-typofix later to maint).
|
||||
(merge 68d40f30c4 dj/typofix-merge-strat later to maint).
|
||||
(merge f66e0401ab jk/optim-in-pack-idx-conversion later to maint).
|
||||
(merge 169bed7421 rs/parse-options-dup-null-fix later to maint).
|
||||
(merge 51bd6be32d rs/use-copy-array-in-mingw-shell-command-preparation later to maint).
|
||||
(merge b018719927 ma/t7004 later to maint).
|
||||
(merge 932757b0cc ar/install-doc-update-cmds-needing-the-shell later to maint).
|
||||
(merge 46efd28be1 ep/guard-kset-tar-headers later to maint).
|
||||
(merge 9e5afdf997 ec/fetch-mark-common-refs-trace2 later to maint).
|
||||
(merge f0e58b3fe8 pb/submodule-update-fetches later to maint).
|
||||
(merge 2a02262078 dl/t5520-cleanup later to maint).
|
||||
(merge a4fb016ba1 js/pkt-line-h-typofix later to maint).
|
||||
(merge 54a7a64613 rs/simplify-prepare-cmd later to maint).
|
||||
(merge 3eae30e464 jk/lore-is-the-archive later to maint).
|
||||
(merge 14b7664df8 dl/lore-is-the-archive later to maint).
|
||||
(merge 0e40a73a4c po/bundle-doc-clonable later to maint).
|
||||
(merge e714b898c6 as/t7812-missing-redirects-fix later to maint).
|
||||
(merge 528d9e6d01 jk/perf-wo-git-dot-pm later to maint).
|
||||
(merge fc42f20e24 sg/test-squelch-noise-in-commit-bulk later to maint).
|
||||
(merge c64368e3a2 bc/t9001-zsh-in-posix-emulation-mode later to maint).
|
||||
(merge 11de8dd7ef dr/branch-usage-casefix later to maint).
|
||||
(merge e05e8cf074 rs/archive-zip-code-cleanup later to maint).
|
||||
(merge 147ee35558 rs/commit-export-env-simplify later to maint).
|
||||
(merge 4507ecc771 rs/patch-id-use-oid-to-hex later to maint).
|
||||
(merge 51a0a4ed95 mr/bisect-use-after-free later to maint).
|
||||
(merge cc2bd5c45d pb/submodule-doc-xref later to maint).
|
||||
(merge df5be01669 ja/doc-markup-cleanup later to maint).
|
||||
(merge 7c5cea7242 mr/bisect-save-pointer-to-const-string later to maint).
|
||||
(merge 20a67e8ce9 js/use-test-tool-on-path later to maint).
|
||||
(merge 4e61b2214d ew/packfile-syscall-optim later to maint).
|
||||
(merge ace0f86c7f pb/clarify-line-log-doc later to maint).
|
||||
(merge 763a59e71c en/merge-recursive-oid-eq-simplify later to maint).
|
||||
(merge 4e2c4c0d4f do/gitweb-typofix-in-comments later to maint).
|
||||
(merge 421c0ffb02 jb/doc-multi-pack-idx-fix later to maint).
|
||||
(merge f8740c586b pm/am-in-body-header-doc-update later to maint).
|
||||
(merge 5814d44d9b tm/doc-submodule-absorb-fix later to maint).
|
||||
|
|
@ -1,55 +0,0 @@
|
|||
Git 2.25.1 Release Notes
|
||||
========================
|
||||
|
||||
Fixes since v2.25
|
||||
-----------------
|
||||
|
||||
* "git commit" gives output similar to "git status" when there is
|
||||
nothing to commit, but without honoring the advise.statusHints
|
||||
configuration variable, which has been corrected.
|
||||
|
||||
* has_object_file() said "no" given an object registered to the
|
||||
system via pretend_object_file(), making it inconsistent with
|
||||
read_object_file(), causing lazy fetch to attempt fetching an
|
||||
empty tree from promisor remotes.
|
||||
|
||||
* The code that tries to skip over the entries for the paths in a
|
||||
single directory using the cache-tree was not careful enough
|
||||
against corrupt index file.
|
||||
|
||||
* Complete an update to tutorial that encourages "git switch" over
|
||||
"git checkout" that was done only half-way.
|
||||
|
||||
* Reduce unnecessary round-trip when running "ls-remote" over the
|
||||
stateless RPC mechanism.
|
||||
|
||||
* "git restore --staged" did not correctly update the cache-tree
|
||||
structure, resulting in bogus trees to be written afterwards, which
|
||||
has been corrected.
|
||||
|
||||
* The code recently added to move to the entry beyond the ones in the
|
||||
same directory in the index in the sparse-cone mode did not count
|
||||
the number of entries to skip over incorrectly, which has been
|
||||
corrected.
|
||||
|
||||
* Work around test breakages caused by custom regex engine used in
|
||||
libasan, when address sanitizer is used with more recent versions
|
||||
of gcc and clang.
|
||||
|
||||
* "git fetch --refmap=" option has got a better documentation.
|
||||
|
||||
* Corner case bugs in "git clean" that stems from a (necessarily for
|
||||
performance reasons) awkward calling convention in the directory
|
||||
enumeration API has been corrected.
|
||||
|
||||
* "git grep --no-index" should not get affected by the contents of
|
||||
the .gitmodules file but when "--recurse-submodules" is given or
|
||||
the "submodule.recurse" variable is set, it did. Now these
|
||||
settings are ignored in the "--no-index" mode.
|
||||
|
||||
* Technical details of the bundle format has been documented.
|
||||
|
||||
* Unhelpful warning messages during documentation build have been
|
||||
squelched.
|
||||
|
||||
Also contains various documentation updates, code clean-ups and minor fixups.
|
||||
|
|
@ -1,60 +0,0 @@
|
|||
Git 2.25.2 Release Notes
|
||||
========================
|
||||
|
||||
Fixes since v2.25.1
|
||||
-------------------
|
||||
|
||||
* Minor bugfixes to "git add -i" that has recently been rewritten in C.
|
||||
|
||||
* An earlier update to show the location of working tree in the error
|
||||
message did not consider the possibility that a git command may be
|
||||
run in a bare repository, which has been corrected.
|
||||
|
||||
* The "--recurse-submodules" option of various subcommands did not
|
||||
work well when run in an alternate worktree, which has been
|
||||
corrected.
|
||||
|
||||
* Running "git rm" on a submodule failed unnecessarily when
|
||||
.gitmodules is only cache-dirty, which has been corrected.
|
||||
|
||||
* "git rebase -i" identifies existing commits in its todo file with
|
||||
their abbreviated object name, which could become ambigous as it
|
||||
goes to create new commits, and has a mechanism to avoid ambiguity
|
||||
in the main part of its execution. A few other cases however were
|
||||
not covered by the protection against ambiguity, which has been
|
||||
corrected.
|
||||
|
||||
* The index-pack code now diagnoses a bad input packstream that
|
||||
records the same object twice when it is used as delta base; the
|
||||
code used to declare a software bug when encountering such an
|
||||
input, but it is an input error.
|
||||
|
||||
* The code to automatically shrink the fan-out in the notes tree had
|
||||
an off-by-one bug, which has been killed.
|
||||
|
||||
* "git check-ignore" did not work when the given path is explicitly
|
||||
marked as not ignored with a negative entry in the .gitignore file.
|
||||
|
||||
* The merge-recursive machinery failed to refresh the cache entry for
|
||||
a merge result in a couple of places, resulting in an unnecessary
|
||||
merge failure, which has been fixed.
|
||||
|
||||
* Fix for a bug revealed by a recent change to make the protocol v2
|
||||
the default.
|
||||
|
||||
* "git merge signed-tag" while lacking the public key started to say
|
||||
"No signature", which was utterly wrong. This regression has been
|
||||
reverted.
|
||||
|
||||
* MinGW's poll() emulation has been improved.
|
||||
|
||||
* "git show" and others gave an object name in raw format in its
|
||||
error output, which has been corrected to give it in hex.
|
||||
|
||||
* Both "git ls-remote -h" and "git grep -h" give short usage help,
|
||||
like any other Git subcommand, but it is not unreasonable to expect
|
||||
that the former would behave the same as "git ls-remote --head"
|
||||
(there is no other sensible behaviour for the latter). The
|
||||
documentation has been updated in an attempt to clarify this.
|
||||
|
||||
Also contains various documentation updates, code clean-ups and minor fixups.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
Git v2.25.3 Release Notes
|
||||
=========================
|
||||
|
||||
This release merges the security fix that appears in v2.17.4; see
|
||||
the release notes for that version for details.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
Git v2.25.4 Release Notes
|
||||
=========================
|
||||
|
||||
This release merges the security fix that appears in v2.17.5; see
|
||||
the release notes for that version for details.
|
||||
341
third_party/git/Documentation/RelNotes/2.26.0.txt
vendored
341
third_party/git/Documentation/RelNotes/2.26.0.txt
vendored
|
|
@ -1,341 +0,0 @@
|
|||
Git 2.26 Release Notes
|
||||
======================
|
||||
|
||||
Updates since v2.25
|
||||
-------------------
|
||||
|
||||
Backward compatibility notes
|
||||
|
||||
* "git rebase" uses a different backend that is based on the 'merge'
|
||||
machinery by default. There are a few known differences in the
|
||||
behaviour from the traditional machinery based on patch+apply.
|
||||
|
||||
If your workflow is negatively affected by this change, please
|
||||
report it to git@vger.kernel.org so that we can take a look into
|
||||
it. After doing so, you can set the 'rebase.backend' configuration
|
||||
variable to 'apply', in order to use the old default behaviour in
|
||||
the meantime.
|
||||
|
||||
|
||||
UI, Workflows & Features
|
||||
|
||||
* Sample credential helper for using .netrc has been updated to work
|
||||
out of the box.
|
||||
|
||||
* gpg.minTrustLevel configuration variable has been introduced to
|
||||
tell various signature verification codepaths the required minimum
|
||||
trust level.
|
||||
|
||||
* The command line completion (in contrib/) learned to complete
|
||||
subcommands and arguments to "git worktree".
|
||||
|
||||
* Disambiguation logic to tell revisions and pathspec apart has been
|
||||
tweaked so that backslash-escaped glob special characters do not
|
||||
count in the "wildcards are pathspec" rule.
|
||||
|
||||
* One effect of specifying where the GIT_DIR is (either with the
|
||||
environment variable, or with the "git --git-dir=<where> cmd"
|
||||
option) is to disable the repository discovery. This has been
|
||||
placed a bit more stress in the documentation, as new users often
|
||||
get confused.
|
||||
|
||||
* Two help messages given when "git add" notices the user gave it
|
||||
nothing to add have been updated to use advise() API.
|
||||
|
||||
* A new version of fsmonitor-watchman hook has been introduced, to
|
||||
avoid races.
|
||||
|
||||
* "git config" learned to show in which "scope", in addition to in
|
||||
which file, each config setting comes from.
|
||||
|
||||
* The basic 7 colors learned the brighter counterparts
|
||||
(e.g. "brightred").
|
||||
|
||||
* "git sparse-checkout" learned a new "add" subcommand.
|
||||
|
||||
* A configuration element used for credential subsystem can now use
|
||||
wildcard pattern to specify for which set of URLs the entry
|
||||
applies.
|
||||
|
||||
* "git clone --recurse-submodules --single-branch" now uses the same
|
||||
single-branch option when cloning the submodules.
|
||||
|
||||
* "git rm" and "git stash" learns the new "--pathspec-from-file"
|
||||
option.
|
||||
|
||||
* "git am --show-current-patch" is a way to show the piece of e-mail
|
||||
for the stopped step, which is not suitable to directly feed "git
|
||||
apply" (it is designed to be a good "git am" input). It learned a
|
||||
new option to show only the patch part.
|
||||
|
||||
* Handling of conflicting renames in merge-recursive have further
|
||||
been made consistent with how existing codepaths try to mimic what
|
||||
is done to add/add conflicts.
|
||||
|
||||
|
||||
Performance, Internal Implementation, Development Support etc.
|
||||
|
||||
* Tell .editorconfig that in this project, *.txt files are indented
|
||||
with tabs.
|
||||
|
||||
* The test-lint machinery knew to check "VAR=VAL shell_function"
|
||||
construct, but did not check "VAR= shell_function", which has been
|
||||
corrected.
|
||||
|
||||
* Replace "git config --bool" calls with "git config --type=bool" in
|
||||
sample templates.
|
||||
|
||||
* The effort to move "git-add--interactive" to C continues.
|
||||
|
||||
* Improve error message generation for "git submodule add".
|
||||
|
||||
* Preparation of test scripts for the day when the object names will
|
||||
use SHA-256 continues.
|
||||
|
||||
* Warn programmers about pretend_object_file() that allows the code
|
||||
to tentatively use in-core objects.
|
||||
|
||||
* The way "git pack-objects" reuses objects stored in existing pack
|
||||
to generate its result has been improved.
|
||||
|
||||
* The transport protocol version 2 becomes the default one.
|
||||
|
||||
* Traditionally, we avoided threaded grep while searching in objects
|
||||
(as opposed to files in the working tree) as accesses to the object
|
||||
layer is not thread-safe. This limitation is getting lifted.
|
||||
|
||||
* "git rebase -i" (and friends) used to unnecessarily check out the
|
||||
tip of the branch to be rebased, which has been corrected.
|
||||
|
||||
* A low-level API function get_oid(), that accepts various ways to
|
||||
name an object, used to issue end-user facing error messages
|
||||
without l10n, which has been updated to be translatable.
|
||||
|
||||
* Unneeded connectivity check is now disabled in a partial clone when
|
||||
fetching into it.
|
||||
|
||||
* Some rough edges in the sparse-checkout feature, especially around
|
||||
the cone mode, have been cleaned up.
|
||||
|
||||
* The diff-* plumbing family of subcommands now pay attention to the
|
||||
diff.wsErrorHighlight configuration, which has been ignored before;
|
||||
this allows "git add -p" to also show the whitespace problems to
|
||||
the end user.
|
||||
|
||||
* Some codepaths were given a repository instance as a parameter to
|
||||
work in the repository, but passed the_repository instance to its
|
||||
callees, which has been cleaned up (somewhat).
|
||||
|
||||
* Memory footprint and performance of "git name-rev" has been
|
||||
improved.
|
||||
|
||||
* The object reachability bitmap machinery and the partial cloning
|
||||
machinery were not prepared to work well together, because some
|
||||
object-filtering criteria that partial clones use inherently rely
|
||||
on object traversal, but the bitmap machinery is an optimization
|
||||
to bypass that object traversal. There however are some cases
|
||||
where they can work together, and they were taught about them.
|
||||
|
||||
* "git rebase" has learned to use the merge backend (i.e. the
|
||||
machinery that drives "rebase -i") by default, while allowing
|
||||
"--apply" option to use the "apply" backend (e.g. the moral
|
||||
equivalent of "format-patch piped to am"). The rebase.backend
|
||||
configuration variable can be set to customize.
|
||||
|
||||
* Underlying machinery of "git bisect--helper" is being refactored
|
||||
into pieces that are more easily reused.
|
||||
|
||||
|
||||
Fixes since v2.25
|
||||
-----------------
|
||||
|
||||
* "git commit" gives output similar to "git status" when there is
|
||||
nothing to commit, but without honoring the advise.statusHints
|
||||
configuration variable, which has been corrected.
|
||||
|
||||
* has_object_file() said "no" given an object registered to the
|
||||
system via pretend_object_file(), making it inconsistent with
|
||||
read_object_file(), causing lazy fetch to attempt fetching an
|
||||
empty tree from promisor remotes.
|
||||
|
||||
* Complete an update to tutorial that encourages "git switch" over
|
||||
"git checkout" that was done only half-way.
|
||||
|
||||
* C pedantry ;-) fix.
|
||||
|
||||
* The code that tries to skip over the entries for the paths in a
|
||||
single directory using the cache-tree was not careful enough
|
||||
against corrupt index file.
|
||||
|
||||
* Reduce unnecessary round-trip when running "ls-remote" over the
|
||||
stateless RPC mechanism.
|
||||
|
||||
* "git restore --staged" did not correctly update the cache-tree
|
||||
structure, resulting in bogus trees to be written afterwards, which
|
||||
has been corrected.
|
||||
|
||||
* The code recently added to move to the entry beyond the ones in the
|
||||
same directory in the index in the sparse-cone mode did not count
|
||||
the number of entries to skip over incorrectly, which has been
|
||||
corrected.
|
||||
|
||||
* Rendering by "git log --graph" of ancestry lines leading to a merge
|
||||
commit were made suboptimal to waste vertical space a bit with a
|
||||
recent update, which has been corrected.
|
||||
|
||||
* Work around test breakages caused by custom regex engine used in
|
||||
libasan, when address sanitizer is used with more recent versions
|
||||
of gcc and clang.
|
||||
|
||||
* Minor bugfixes to "git add -i" that has recently been rewritten in C.
|
||||
|
||||
* "git fetch --refmap=" option has got a better documentation.
|
||||
|
||||
* "git checkout X" did not correctly fail when X is not a local
|
||||
branch but could name more than one remote-tracking branches
|
||||
(i.e. to be dwimmed as the starting point to create a corresponding
|
||||
local branch), which has been corrected.
|
||||
(merge fa74180d08 am/checkout-file-and-ref-ref-ambiguity later to maint).
|
||||
|
||||
* Corner case bugs in "git clean" that stems from a (necessarily for
|
||||
performance reasons) awkward calling convention in the directory
|
||||
enumeration API has been corrected.
|
||||
|
||||
* A fetch that is told to recursively fetch updates in submodules
|
||||
inevitably produces reams of output, and it becomes hard to spot
|
||||
error messages. The command has been taught to enumerate
|
||||
submodules that had errors at the end of the operation.
|
||||
(merge 0222540827 es/fetch-show-failed-submodules-atend later to maint).
|
||||
|
||||
* The "--recurse-submodules" option of various subcommands did not
|
||||
work well when run in an alternate worktree, which has been
|
||||
corrected.
|
||||
|
||||
* Futureproofing a test not to depend on the current implementation
|
||||
detail.
|
||||
|
||||
* Running "git rm" on a submodule failed unnecessarily when
|
||||
.gitmodules is only cache-dirty, which has been corrected.
|
||||
|
||||
* C pedantry ;-) fix.
|
||||
|
||||
* "git grep --no-index" should not get affected by the contents of
|
||||
the .gitmodules file but when "--recurse-submodules" is given or
|
||||
the "submodule.recurse" variable is set, it did. Now these
|
||||
settings are ignored in the "--no-index" mode.
|
||||
|
||||
* Technical details of the bundle format has been documented.
|
||||
|
||||
* Unhelpful warning messages during documentation build have been squelched.
|
||||
|
||||
* "git rebase -i" identifies existing commits in its todo file with
|
||||
their abbreviated object name, which could become ambiguous as it
|
||||
goes to create new commits, and has a mechanism to avoid ambiguity
|
||||
in the main part of its execution. A few other cases however were
|
||||
not covered by the protection against ambiguity, which has been
|
||||
corrected.
|
||||
|
||||
* Allow the rebase.missingCommitsCheck configuration to kick in when
|
||||
"rebase --edit-todo" and "rebase --continue" restarts the procedure.
|
||||
(merge 5a5445d878 ag/edit-todo-drop-check later to maint).
|
||||
|
||||
* The way "git submodule status" reports an initialized but not yet
|
||||
populated submodule has not been reimplemented correctly when a
|
||||
part of the "git submodule" command was rewritten in C, which has
|
||||
been corrected.
|
||||
(merge f38c92452d pk/status-of-uncloned-submodule later to maint).
|
||||
|
||||
* The code to automatically shrink the fan-out in the notes tree had
|
||||
an off-by-one bug, which has been killed.
|
||||
|
||||
* The index-pack code now diagnoses a bad input packstream that
|
||||
records the same object twice when it is used as delta base; the
|
||||
code used to declare a software bug when encountering such an
|
||||
input, but it is an input error.
|
||||
|
||||
|
||||
* The code to compute the commit-graph has been taught to use a more
|
||||
robust way to tell if two object directories refer to the same
|
||||
thing.
|
||||
(merge a7df60cac8 tb/commit-graph-object-dir later to maint).
|
||||
|
||||
* "git remote rename X Y" needs to adjust configuration variables
|
||||
(e.g. branch.<name>.remote) whose value used to be X to Y.
|
||||
branch.<name>.pushRemote is now also updated.
|
||||
|
||||
* Update to doc-diff.
|
||||
|
||||
* Doc markup fix.
|
||||
|
||||
* "git check-ignore" did not work when the given path is explicitly
|
||||
marked as not ignored with a negative entry in the .gitignore file.
|
||||
|
||||
* The merge-recursive machinery failed to refresh the cache entry for
|
||||
a merge result in a couple of places, resulting in an unnecessary
|
||||
merge failure, which has been fixed.
|
||||
|
||||
* Fix for a bug revealed by a recent change to make the protocol v2
|
||||
the default.
|
||||
|
||||
* In rare cases "git worktree add <path>" could think that <path>
|
||||
was already a registered worktree even when it wasn't and refuse
|
||||
to add the new worktree. This has been corrected.
|
||||
(merge bb69b3b009 es/worktree-avoid-duplication-fix later to maint).
|
||||
|
||||
* "git push" should stop from updating a branch that is checked out
|
||||
when receive.denyCurrentBranch configuration is set, but it failed
|
||||
to pay attention to checkouts in secondary worktrees. This has
|
||||
been corrected.
|
||||
(merge 4d864895a2 hv/receive-denycurrent-everywhere later to maint).
|
||||
|
||||
* "git rebase BASE BRANCH" rebased/updated the tip of BRANCH and
|
||||
checked it out, even when the BRANCH is checked out in a different
|
||||
worktree. This has been corrected.
|
||||
(merge b5cabb4a96 es/do-not-let-rebase-switch-to-protected-branch later to maint).
|
||||
|
||||
* "git describe" in a repository with multiple root commits sometimes
|
||||
gave up looking for the best tag to describe a given commit with
|
||||
too early, which has been adjusted.
|
||||
|
||||
* "git merge signed-tag" while lacking the public key started to say
|
||||
"No signature", which was utterly wrong. This regression has been
|
||||
reverted.
|
||||
|
||||
* MinGW's poll() emulation has been improved.
|
||||
|
||||
* "git show" and others gave an object name in raw format in its
|
||||
error output, which has been corrected to give it in hex.
|
||||
|
||||
* "git fetch" over HTTP walker protocol did not show any progress
|
||||
output. We inherently do not know how much work remains, but still
|
||||
we can show something not to bore users.
|
||||
(merge 7655b4119d rs/show-progress-in-dumb-http-fetch later to maint).
|
||||
|
||||
* Both "git ls-remote -h" and "git grep -h" give short usage help,
|
||||
like any other Git subcommand, but it is not unreasonable to expect
|
||||
that the former would behave the same as "git ls-remote --head"
|
||||
(there is no other sensible behaviour for the latter). The
|
||||
documentation has been updated in an attempt to clarify this.
|
||||
|
||||
* Other code cleanup, docfix, build fix, etc.
|
||||
(merge d0d0a357a1 am/update-pathspec-f-f-tests later to maint).
|
||||
(merge f94f7bd00d am/test-pathspec-f-f-error-cases later to maint).
|
||||
(merge c513a958b6 ss/t6025-modernize later to maint).
|
||||
(merge b441717256 dl/test-must-fail-fixes later to maint).
|
||||
(merge d031049da3 mt/sparse-checkout-doc-update later to maint).
|
||||
(merge 145136a95a jc/skip-prefix later to maint).
|
||||
(merge 5290d45134 jk/alloc-cleanups later to maint).
|
||||
(merge 7a9f8ca805 rs/parse-options-concat-dup later to maint).
|
||||
(merge 517b60564e rs/strbuf-insertstr later to maint).
|
||||
(merge f696a2b1c8 jk/mailinfo-cleanup later to maint).
|
||||
(merge de26f02db1 js/test-avoid-pipe later to maint).
|
||||
(merge a2dc43414c es/doc-mentoring later to maint).
|
||||
(merge 02bbbe9df9 es/worktree-cleanup later to maint).
|
||||
(merge 2ce6d075fa rs/micro-cleanups later to maint).
|
||||
(merge 27f182b3fc rs/blame-typefix-for-fingerprint later to maint).
|
||||
(merge 3c29e21eb0 ma/test-cleanup later to maint).
|
||||
(merge 240fc04f81 ag/rebase-remove-redundant-code later to maint).
|
||||
(merge d68ce906c7 rs/commit-graph-code-simplification later to maint).
|
||||
(merge a51d9e8f07 rj/t1050-use-test-path-is-file later to maint).
|
||||
(merge fd0bc17557 kk/complete-diff-color-moved later to maint).
|
||||
(merge 65bf820d0e en/test-cleanup later to maint).
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
Git v2.26.1 Release Notes
|
||||
=========================
|
||||
|
||||
This release merges the security fix that appears in v2.17.4; see
|
||||
the release notes for that version for details.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
Git v2.26.2 Release Notes
|
||||
=========================
|
||||
|
||||
This release merges the security fix that appears in v2.17.5; see
|
||||
the release notes for that version for details.
|
||||
|
|
@ -12,7 +12,7 @@ Fixes since v2.3.2
|
|||
* Description given by "grep -h" for its --exclude-standard option
|
||||
was phrased poorly.
|
||||
|
||||
* Documentation for "git remote add" mentioned "--tags" and
|
||||
* Documentaton for "git remote add" mentioned "--tags" and
|
||||
"--no-tags" and it was not clear that fetch from the remote in
|
||||
the future will use the default behaviour when neither is given
|
||||
to override it.
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ Git v2.3.7 Release Notes
|
|||
Fixes since v2.3.6
|
||||
------------------
|
||||
|
||||
* An earlier update to the parser that dissects a URL broke an
|
||||
* An earlier update to the parser that disects a URL broke an
|
||||
address, followed by a colon, followed by an empty string (instead
|
||||
of the port number), e.g. ssh://example.com:/path/to/repo.
|
||||
|
||||
|
|
|
|||
|
|
@ -66,7 +66,7 @@ Fixes since v2.4.3
|
|||
* Some time ago, "git blame" (incorrectly) lost the convert_to_git()
|
||||
call when synthesizing a fake "tip" commit that represents the
|
||||
state in the working tree, which broke folks who record the history
|
||||
with LF line ending to make their project portable across
|
||||
with LF line ending to make their project portabile across
|
||||
platforms while terminating lines in their working tree files with
|
||||
CRLF for their platform.
|
||||
|
||||
|
|
|
|||
|
|
@ -172,8 +172,7 @@ Performance, Internal Implementation, Development Support etc.
|
|||
incorrect patch text to "git apply". Add tests to demonstrate
|
||||
this.
|
||||
|
||||
I have a slight suspicion that this may be
|
||||
cf. <7vtzf77wjp.fsf@gitster.siamese.dyndns.org> coming back
|
||||
I have a slight suspicion that this may be $gmane/87202 coming back
|
||||
and biting us (I seem to have said "let's run with this and see
|
||||
what happens" back then).
|
||||
|
||||
|
|
|
|||
|
|
@ -40,7 +40,7 @@ UI, Workflows & Features
|
|||
|
||||
* "git interpret-trailers" can now run outside of a Git repository.
|
||||
|
||||
* "git p4" learned to re-encode the pathname it uses to communicate
|
||||
* "git p4" learned to reencode the pathname it uses to communicate
|
||||
with the p4 depot with a new option.
|
||||
|
||||
* Give progress meter to "git filter-branch".
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ Fixes since v2.7
|
|||
setting GIT_WORK_TREE environment themselves.
|
||||
|
||||
* The "exclude_list" structure has the usual "alloc, nr" pair of
|
||||
fields to be used by ALLOC_GROW(), but clear_pattern_list() forgot
|
||||
fields to be used by ALLOC_GROW(), but clear_exclude_list() forgot
|
||||
to reset 'alloc' to 0 when it cleared 'nr' to discard the managed
|
||||
array.
|
||||
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ Fixes since v2.7.2
|
|||
tests.
|
||||
|
||||
* "git show 'HEAD:Foo[BAR]Baz'" did not interpret the argument as a
|
||||
rev, i.e. the object named by the pathname with wildcard
|
||||
rev, i.e. the object named by the the pathname with wildcard
|
||||
characters in a tree object.
|
||||
|
||||
* "git rev-parse --git-common-dir" used in the worktree feature
|
||||
|
|
|
|||
|
|
@ -189,7 +189,7 @@ Performance, Internal Implementation, Development Support etc.
|
|||
* Some calls to strcpy(3) triggers a false warning from static
|
||||
analyzers that are less intelligent than humans, and reducing the
|
||||
number of these false hits helps us notice real issues. A few
|
||||
calls to strcpy(3) in a couple of programs that are already safe
|
||||
calls to strcpy(3) in a couple of protrams that are already safe
|
||||
has been rewritten to avoid false warnings.
|
||||
|
||||
* The "name_path" API was an attempt to reduce the need to construct
|
||||
|
|
@ -270,7 +270,7 @@ notes for details).
|
|||
setting GIT_WORK_TREE environment themselves.
|
||||
|
||||
* The "exclude_list" structure has the usual "alloc, nr" pair of
|
||||
fields to be used by ALLOC_GROW(), but clear_pattern_list() forgot
|
||||
fields to be used by ALLOC_GROW(), but clear_exclude_list() forgot
|
||||
to reset 'alloc' to 0 when it cleared 'nr' to discard the managed
|
||||
array.
|
||||
|
||||
|
|
|
|||
|
|
@ -55,8 +55,8 @@ Fixes since v2.8.2
|
|||
This is necessary to use Git on Windows shared directories, and is
|
||||
already enabled for the MinGW and plain Windows builds. It also
|
||||
has been used in Cygwin packaged versions of Git for quite a while.
|
||||
See https://lore.kernel.org/git/20160419091055.GF2345@dinwoodie.org/
|
||||
and https://lore.kernel.org/git/20150811100527.GW14466@dinwoodie.org/.
|
||||
See http://thread.gmane.org/gmane.comp.version-control.git/291853
|
||||
and http://thread.gmane.org/gmane.comp.version-control.git/275680.
|
||||
|
||||
* "git replace -e" did not honour "core.editor" configuration.
|
||||
|
||||
|
|
|
|||
|
|
@ -368,7 +368,7 @@ notes for details).
|
|||
This is necessary to use Git on Windows shared directories, and is
|
||||
already enabled for the MinGW and plain Windows builds. It also
|
||||
has been used in Cygwin packaged versions of Git for quite a while.
|
||||
See https://lore.kernel.org/git/20160419091055.GF2345@dinwoodie.org/
|
||||
See http://thread.gmane.org/gmane.comp.version-control.git/291853
|
||||
|
||||
* "merge-octopus" strategy did not ensure that the index is clean
|
||||
when merge begins.
|
||||
|
|
|
|||
|
|
@ -36,7 +36,7 @@ Fixes since v2.9.2
|
|||
* One part of "git am" had an oddball helper function that called
|
||||
stuff from outside "his" as opposed to calling what we have "ours",
|
||||
which was not gender-neutral and also inconsistent with the rest of
|
||||
the system where outside stuff is usually called "theirs" in
|
||||
the system where outside stuff is usuall called "theirs" in
|
||||
contrast to "ours".
|
||||
|
||||
* The test framework learned a new helper test_match_signal to
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue