1f010d6bdf
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>
25 lines
865 B
Plaintext
25 lines
865 B
Plaintext
Git v2.30.2 Release Notes
|
|
=========================
|
|
|
|
This release addresses the security issue CVE-2022-24765.
|
|
|
|
Fixes since v2.30.2
|
|
-------------------
|
|
|
|
* Build fix on Windows.
|
|
|
|
* Fix `GIT_CEILING_DIRECTORIES` with Windows-style root directories.
|
|
|
|
* CVE-2022-24765:
|
|
On multi-user machines, Git users might find themselves
|
|
unexpectedly in a Git worktree, e.g. when another user created a
|
|
repository in `C:\.git`, in a mounted network drive or in a
|
|
scratch space. Merely having a Git-aware prompt that runs `git
|
|
status` (or `git diff`) and navigating to a directory which is
|
|
supposedly not a Git worktree, or opening such a directory in an
|
|
editor or IDE such as VS Code or Atom, will potentially run
|
|
commands defined by that other user.
|
|
|
|
Credit for finding this vulnerability goes to 俞晨东; The fix was
|
|
authored by Johannes Schindelin.
|