
We presently use the ".txt" extension for our AsciiDoc files. While not wrong, most editors do not associate this extension with AsciiDoc, meaning that contributors don't get automatic editor functionality that could be useful, such as syntax highlighting and prose linting. It is much more common to use the ".adoc" extension for AsciiDoc files, since this helps editors automatically detect files and also allows various forges to provide rich (HTML-like) rendering. Let's do that here, renaming all of the files and updating the includes where relevant. Adjust the various build scripts and makefiles to use the new extension as well. Note that this should not result in any user-visible changes to the documentation. Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
19 lines
828 B
Plaintext
19 lines
828 B
Plaintext
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.
|