Git 2.33.5

Signed-off-by: Taylor Blau <me@ttaylorr.com>

.cirrus.yml

@@ -9,7 +9,7 @@ freebsd_12_task:
     DEFAULT_TEST_TARGET: prove
     DEVELOPER: 1
   freebsd_instance:
-    image_family: freebsd-12-3
+    image_family: freebsd-12-2
     memory: 2G
   install_script:
     pkg install -y gettext gmake perl5

.github/workflows/check-whitespace.yml

@@ -1,9 +1,8 @@
 name: check-whitespace
 
-# Get the repository with all commits to ensure that we can analyze
-# all of the commits contributed via the Pull Request.
+# Get the repo with the commits(+1) in the series.
 # Process `git log --check` output to extract just the check errors.
-# Exit with failure upon white-space issues.
+# Add a comment to the pull request with the check errors.
 
 on:
   pull_request:

.github/workflows/l10n.yml

@@ -1,105 +0,0 @@
-name: git-l10n
-
-on: [push, pull_request_target]
-
-jobs:
-  git-po-helper:
-    if: >-
-      endsWith(github.repository, '/git-po') ||
-      contains(github.head_ref, 'l10n') ||
-      contains(github.ref, 'l10n')
-    runs-on: ubuntu-latest
-    permissions:
-      pull-requests: write
-    steps:
-      - name: Setup base and head objects
-        id: setup-tips
-        run: |
-          if test "${{ github.event_name }}" = "pull_request_target"
-          then
-            base=${{ github.event.pull_request.base.sha }}
-            head=${{ github.event.pull_request.head.sha }}
-          else
-            base=${{ github.event.before }}
-            head=${{ github.event.after }}
-          fi
-          echo "::set-output name=base::$base"
-          echo "::set-output name=head::$head"
-      - name: Run partial clone
-        run: |
-          git -c init.defaultBranch=master init --bare .
-          git remote add \
-            --mirror=fetch \
-            origin \
-            https://github.com/${{ github.repository }}
-          # Fetch tips that may be unreachable from github.ref:
-          # - For a forced push, "$base" may be unreachable.
-          # - For a "pull_request_target" event, "$head" may be unreachable.
-          args=
-          for commit in \
-            ${{ steps.setup-tips.outputs.base }} \
-            ${{ steps.setup-tips.outputs.head }}
-          do
-            case $commit in
-            *[^0]*)
-              args="$args $commit"
-              ;;
-            *)
-              # Should not fetch ZERO-OID.
-              ;;
-            esac
-          done
-          git -c protocol.version=2 fetch \
-            --progress \
-            --no-tags \
-            --no-write-fetch-head \
-            --filter=blob:none \
-            origin \
-            ${{ github.ref }} \
-            $args
-      - uses: actions/setup-go@v2
-        with:
-          go-version: '>=1.16'
-      - name: Install git-po-helper
-        run: go install github.com/git-l10n/git-po-helper@main
-      - name: Install other dependencies
-        run: |
-          sudo apt-get update -q &&
-          sudo apt-get install -q -y gettext
-      - name: Run git-po-helper
-        id: check-commits
-        run: |
-          exit_code=0
-          git-po-helper check-commits \
-            --github-action-event="${{ github.event_name }}" -- \
-            ${{ steps.setup-tips.outputs.base }}..${{ steps.setup-tips.outputs.head }} \
-            >git-po-helper.out 2>&1 || exit_code=$?
-          if test $exit_code -ne 0 || grep -q WARNING git-po-helper.out
-          then
-            # Remove ANSI colors which are proper for console logs but not
-            # proper for PR comment.
-            echo "COMMENT_BODY<<EOF" >>$GITHUB_ENV
-            perl -pe 's/\e\[[0-9;]*m//g; s/\bEOF$//g' git-po-helper.out >>$GITHUB_ENV
-            echo "EOF" >>$GITHUB_ENV
-          fi
-          cat git-po-helper.out
-          exit $exit_code
-      - name: Create comment in pull request for report
-        uses: mshick/add-pr-comment@v1
-        if: >-
-          always() &&
-          github.event_name == 'pull_request_target' &&
-          env.COMMENT_BODY != ''
-        with:
-          repo-token: ${{ secrets.GITHUB_TOKEN }}
-          repo-token-user-login: 'github-actions[bot]'
-          message: >
-            ${{ steps.check-commits.outcome == 'failure' && 'Errors and warnings' || 'Warnings' }}
-            found by [git-po-helper](https://github.com/git-l10n/git-po-helper#readme) in workflow
-            [#${{ github.run_number }}](${{ env.GITHUB_SERVER_URL }}/${{ github.repository }}/actions/runs/${{ github.run_id }}):
-
-            ```
-
-            ${{ env.COMMENT_BODY }}
-
-            ```

.github/workflows/main.yml

@@ -1,4 +1,4 @@
-name: CI
+name: CI/PR
 
 on: [push, pull_request]
 
@@ -7,7 +7,6 @@ env:
 
 jobs:
   ci-config:
-    name: config
     runs-on: ubuntu-latest
     outputs:
       enabled: ${{ steps.check-ref.outputs.enabled }}${{ steps.skip-if-redundant.outputs.enabled }}
@@ -78,7 +77,6 @@ jobs:
             }
 
   windows-build:
-    name: win build
     needs: ci-config
     if: needs.ci-config.outputs.enabled == 'yes'
     runs-on: windows-latest
@@ -90,7 +88,7 @@ jobs:
       env:
         HOME: ${{runner.workspace}}
         NO_PERL: 1
-      run: . /etc/profile && ci/make-test-artifacts.sh artifacts
+      run: ci/make-test-artifacts.sh artifacts
     - name: zip up tracked files
       run: git archive -o artifacts/tracked.tar.gz HEAD
     - name: upload tracked files and build artifacts
@@ -99,7 +97,6 @@ jobs:
         name: windows-artifacts
         path: artifacts
   windows-test:
-    name: win test
     runs-on: windows-latest
     needs: [windows-build]
     strategy:
@@ -118,9 +115,9 @@ jobs:
     - uses: git-for-windows/setup-git-for-windows-sdk@v1
     - name: test
       shell: bash
-      run: . /etc/profile && ci/run-test-slice.sh ${{matrix.nr}} 10
-    - name: print test failures
-      if: failure() && env.FAILED_TEST_ARTIFACTS != ''
+      run: ci/run-test-slice.sh ${{matrix.nr}} 10
+    - name: ci/print-test-failures.sh
+      if: failure()
       shell: bash
       run: ci/print-test-failures.sh
     - name: Upload failed tests' directories
@@ -130,7 +127,6 @@ jobs:
         name: failed-tests-windows
         path: ${{env.FAILED_TEST_ARTIFACTS}}
   vs-build:
-    name: win+VS build
     needs: ci-config
     if: needs.ci-config.outputs.enabled == 'yes'
     env:
@@ -182,7 +178,6 @@ jobs:
         name: vs-artifacts
         path: artifacts
   vs-test:
-    name: win+VS test
     runs-on: windows-latest
     needs: vs-build
     strategy:
@@ -203,9 +198,10 @@ jobs:
       shell: bash
       env:
         NO_SVN_TESTS: 1
-      run: . /etc/profile && ci/run-test-slice.sh ${{matrix.nr}} 10
-    - name: print test failures
-      if: failure() && env.FAILED_TEST_ARTIFACTS != ''
+        GIT_TEST_SKIP_REBASE_P: 1
+      run: ci/run-test-slice.sh ${{matrix.nr}} 10
+    - name: ci/print-test-failures.sh
+      if: failure()
       shell: bash
       run: ci/print-test-failures.sh
     - name: Upload failed tests' directories
@@ -215,7 +211,6 @@ jobs:
         name: failed-tests-windows
         path: ${{env.FAILED_TEST_ARTIFACTS}}
   regular:
-    name: ${{matrix.vector.jobname}} (${{matrix.vector.pool}})
     needs: ci-config
     if: needs.ci-config.outputs.enabled == 'yes'
     strategy:
@@ -225,46 +220,28 @@ jobs:
           - jobname: linux-clang
             cc: clang
             pool: ubuntu-latest
-          - jobname: linux-sha256
-            cc: clang
-            os: ubuntu
-            pool: ubuntu-latest
           - jobname: linux-gcc
             cc: gcc
-            cc_package: gcc-8
-            pool: ubuntu-latest
-          - jobname: linux-TEST-vars
-            cc: gcc
-            os: ubuntu
-            cc_package: gcc-8
             pool: ubuntu-latest
           - jobname: osx-clang
             cc: clang
             pool: macos-latest
           - jobname: osx-gcc
             cc: gcc
-            cc_package: gcc-9
             pool: macos-latest
           - jobname: linux-gcc-default
             cc: gcc
             pool: ubuntu-latest
-          - jobname: linux-leaks
-            cc: gcc
-            pool: ubuntu-latest
     env:
       CC: ${{matrix.vector.cc}}
-      CC_PACKAGE: ${{matrix.vector.cc_package}}
       jobname: ${{matrix.vector.jobname}}
-      runs_on_pool: ${{matrix.vector.pool}}
     runs-on: ${{matrix.vector.pool}}
     steps:
     - uses: actions/checkout@v2
     - run: ci/install-dependencies.sh
     - run: ci/run-build-and-tests.sh
-    - name: print test failures
-      if: failure() && env.FAILED_TEST_ARTIFACTS != ''
-      shell: bash
-      run: ci/print-test-failures.sh
+    - run: ci/print-test-failures.sh
+      if: failure()
     - name: Upload failed tests' directories
       if: failure() && env.FAILED_TEST_ARTIFACTS != ''
       uses: actions/upload-artifact@v2
@@ -272,7 +249,6 @@ jobs:
         name: failed-tests-${{matrix.vector.jobname}}
         path: ${{env.FAILED_TEST_ARTIFACTS}}
   dockerized:
-    name: ${{matrix.vector.jobname}} (${{matrix.vector.image}})
     needs: ci-config
     if: needs.ci-config.outputs.enabled == 'yes'
     strategy:
@@ -281,8 +257,7 @@ jobs:
         vector:
         - jobname: linux-musl
           image: alpine
-        - jobname: linux32
-          os: ubuntu32
+        - jobname: Linux32
           image: daald/ubuntu32:xenial
         - jobname: pedantic
           image: fedora
@@ -294,10 +269,8 @@ jobs:
     - uses: actions/checkout@v1
     - run: ci/install-docker-dependencies.sh
     - run: ci/run-build-and-tests.sh
-    - name: print test failures
-      if: failure() && env.FAILED_TEST_ARTIFACTS != ''
-      shell: bash
-      run: ci/print-test-failures.sh
+    - run: ci/print-test-failures.sh
+      if: failure()
     - name: Upload failed tests' directories
       if: failure() && env.FAILED_TEST_ARTIFACTS != ''
       uses: actions/upload-artifact@v1
@@ -314,7 +287,6 @@ jobs:
     - uses: actions/checkout@v2
     - run: ci/install-dependencies.sh
     - run: ci/run-static-analysis.sh
-    - run: ci/check-directional-formatting.bash
   sparse:
     needs: ci-config
     if: needs.ci-config.outputs.enabled == 'yes'
@@ -336,7 +308,6 @@ jobs:
       run: ci/install-dependencies.sh
     - run: make sparse
   documentation:
-    name: documentation
     needs: ci-config
     if: needs.ci-config.outputs.enabled == 'yes'
     env:

.gitignore

@@ -72,13 +72,11 @@
 /git-format-patch
 /git-fsck
 /git-fsck-objects
-/git-fsmonitor--daemon
 /git-gc
 /git-get-tar-commit-id
 /git-grep
 /git-hash-object
 /git-help
-/git-hook
 /git-http-backend
 /git-http-fetch
 /git-http-push
@@ -127,6 +125,7 @@
 /git-range-diff
 /git-read-tree
 /git-rebase
+/git-rebase--preserve-merges
 /git-receive-pack
 /git-reflog
 /git-remote
@@ -191,7 +190,6 @@
 /gitweb/static/gitweb.min.*
 /config-list.h
 /command-list.h
-/hook-list.h
 *.tar.gz
 *.dsc
 *.deb
@@ -200,7 +198,6 @@
 *.[aos]
 *.o.json
 *.py[co]
-.build/
 .depend/
 *.gcda
 *.gcno
@@ -227,7 +224,6 @@
 *.lib
 *.res
 *.sln
-*.sp
 *.suo
 *.ncb
 *.vcproj

.mailmap

@@ -59,9 +59,8 @@ David Reiss <dreiss@facebook.com> <dreiss@dreiss-vmware.(none)>
 David S. Miller <davem@davemloft.net>
 David Turner <novalis@novalis.org> <dturner@twopensource.com>
 David Turner <novalis@novalis.org> <dturner@twosigma.com>
-Derrick Stolee <derrickstolee@github.com> <stolee@gmail.com>
-Derrick Stolee <derrickstolee@github.com> Derrick Stolee via GitGitGadget <gitgitgadget@gmail.com>
-Derrick Stolee <derrickstolee@github.com> <dstolee@microsoft.com>
+Derrick Stolee <dstolee@microsoft.com> <stolee@gmail.com>
+Derrick Stolee <dstolee@microsoft.com> Derrick Stolee via GitGitGadget <gitgitgadget@gmail.com>
 Deskin Miller <deskinm@umich.edu>
 Đoàn Trần Công Danh <congdanhqx@gmail.com> Doan Tran Cong Danh
 Dirk Süsserott <newsletter@dirk.my1.cc>

.travis.yml

@@ -0,0 +1,60 @@
+language: c
+
+cache:
+  directories:
+    - $HOME/travis-cache
+
+os:
+  - linux
+  - osx
+
+osx_image: xcode10.1
+
+compiler:
+  - clang
+  - gcc
+
+matrix:
+  include:
+    - env: jobname=linux-gcc-default
+      os: linux
+      compiler:
+      addons:
+      before_install:
+    - env: jobname=linux-gcc-4.8
+      os: linux
+      dist: trusty
+      compiler:
+    - env: jobname=Linux32
+      os: linux
+      compiler:
+      addons:
+      services:
+        - docker
+      before_install:
+      script: ci/run-docker.sh
+    - env: jobname=linux-musl
+      os: linux
+      compiler:
+      addons:
+      services:
+        - docker
+      before_install:
+      script: ci/run-docker.sh
+    - env: jobname=StaticAnalysis
+      os: linux
+      compiler:
+      script: ci/run-static-analysis.sh
+      after_failure:
+    - env: jobname=Documentation
+      os: linux
+      compiler:
+      script: ci/test-documentation.sh
+      after_failure:
+
+before_install: ci/install-dependencies.sh
+script: ci/run-build-and-tests.sh
+after_failure: ci/print-test-failures.sh
+
+notifications:
+  email: false

CODE_OF_CONDUCT.md

@@ -70,8 +70,8 @@ git@sfconservancy.org, or individually:
 
   - Ævar Arnfjörð Bjarmason <avarab@gmail.com>
   - Christian Couder <christian.couder@gmail.com>
+  - Jeff King <peff@peff.net>
   - Junio C Hamano <gitster@pobox.com>
-  - Taylor Blau <me@ttaylorr.com>
 
 All complaints will be reviewed and investigated promptly and fairly.
 

Documentation/.gitignore

@@ -14,5 +14,4 @@ manpage-base-url.xsl
 SubmittingPatches.txt
 tmp-doc-diff/
 GIT-ASCIIDOCFLAGS
-/.build/
 /GIT-EXCLUDED-PROGRAMS

Documentation/CodingGuidelines

@@ -26,13 +26,6 @@ code.  For Git in general, a few rough rules are:
    go and fix it up."
    Cf. http://lkml.iu.edu/hypermail/linux/kernel/1001.3/01069.html
 
- - Log messages to explain your changes are as important as the
-   changes themselves.  Clearly written code and in-code comments
-   explain how the code works and what is assumed from the surrounding
-   context.  The log messages explain what the changes wanted to
-   achieve and why the changes were necessary (more on this in the
-   accompanying SubmittingPatches document).
-
 Make your code readable and sensible, and don't try to be clever.
 
 As for more concrete guidelines, just imitate the existing code
@@ -43,10 +36,7 @@ the overall style of existing code. Modifications to existing
 code is expected to match the style the surrounding code already
 uses (even if it doesn't match the overall style of existing code).
 
-But if you must have a list of rules, here are some language
-specific ones. Note that Documentation/ToolsForGit.txt document
-has a collection of tips to help you use some external tools
-to conform to these guidelines.
+But if you must have a list of rules, here they are.
 
 For shell scripts specifically (not exhaustive):
 
@@ -220,9 +210,6 @@ For C programs:
    . since mid 2017 with 512f41cf, we have been using designated
      initializers for array (e.g. "int array[10] = { [5] = 2 }").
 
-   . since early 2021 with 765dc168882, we have been using variadic
-     macros, mostly for printf-like trace and debug macros.
-
    These used to be forbidden, but we have not heard any breakage
    report, and they are assumed to be safe.
 
@@ -230,10 +217,7 @@ For C programs:
    the first statement (i.e. -Wdeclaration-after-statement).
 
  - Declaring a variable in the for loop "for (int i = 0; i < 10; i++)"
-   is still not allowed in this codebase.  We are in the process of
-   allowing it by waiting to see that 44ba10d6 (revision: use C99
-   declaration of variable in for() loop, 2021-11-14) does not get
-   complaints.  Let's revisit this around November 2022.
+   is still not allowed in this codebase.
 
  - NULL pointers shall be written as NULL, not as 0.
 
@@ -495,6 +479,17 @@ For Perl programs:
 
  - Learn and use Git.pm if you need that functionality.
 
+ - For Emacs, it's useful to put the following in
+   GIT_CHECKOUT/.dir-locals.el, assuming you use cperl-mode:
+
+    ;; note the first part is useful for C editing, too
+    ((nil . ((indent-tabs-mode . t)
+                  (tab-width . 8)
+                  (fill-column . 80)))
+     (cperl-mode . ((cperl-indent-level . 8)
+                    (cperl-extra-newline-before-brace . nil)
+                    (cperl-merge-trailing-else . t))))
+
 For Python scripts:
 
  - We follow PEP-8 (http://www.python.org/dev/peps/pep-0008/).
@@ -504,33 +499,6 @@ For Python scripts:
  - Where required libraries do not restrict us to Python 2, we try to
    also be compatible with Python 3.1 and later.
 
-
-Program Output
-
- We make a distinction between a Git command's primary output and
- output which is merely chatty feedback (for instance, status
- messages, running transcript, or progress display), as well as error
- messages. Roughly speaking, a Git command's primary output is that
- which one might want to capture to a file or send down a pipe; its
- chatty output should not interfere with these use-cases.
-
- As such, primary output should be sent to the standard output stream
- (stdout), and chatty output should be sent to the standard error
- stream (stderr). Examples of commands which produce primary output
- include `git log`, `git show`, and `git branch --list` which generate
- output on the stdout stream.
-
- Not all Git commands have primary output; this is often true of
- commands whose main function is to perform an action. Some action
- commands are silent, whereas others are chatty. An example of a
- chatty action commands is `git clone` with its "Cloning into
- '<path>'..." and "Checking connectivity..." status messages which it
- sends to the stderr stream.
-
- Error messages from Git commands should always be sent to the stderr
- stream.
-
-
 Error Messages
 
  - Do not end error messages with a full stop.

Documentation/Makefile

@@ -1,6 +1,3 @@
-# Import tree-wide shared Makefile behavior and libraries
-include ../shared.mak
-
 # Guard against environment variables
 MAN1_TXT =
 MAN5_TXT =
@@ -93,9 +90,6 @@ SP_ARTICLES += $(API_DOCS)
 TECH_DOCS += MyFirstContribution
 TECH_DOCS += MyFirstObjectWalk
 TECH_DOCS += SubmittingPatches
-TECH_DOCS += ToolsForGit
-TECH_DOCS += technical/bundle-format
-TECH_DOCS += technical/cruft-packs
 TECH_DOCS += technical/hash-function-transition
 TECH_DOCS += technical/http-protocol
 TECH_DOCS += technical/index-format
@@ -220,6 +214,33 @@ DEFAULT_EDITOR_SQ = $(subst ','\'',$(DEFAULT_EDITOR))
 ASCIIDOC_EXTRA += -a 'git-default-editor=$(DEFAULT_EDITOR_SQ)'
 endif
 
+QUIET_SUBDIR0  = +$(MAKE) -C # space to separate -C and subdir
+QUIET_SUBDIR1  =
+
+ifneq ($(findstring $(MAKEFLAGS),w),w)
+PRINT_DIR = --no-print-directory
+else # "make -w"
+NO_SUBDIR = :
+endif
+
+ifneq ($(findstring $(MAKEFLAGS),s),s)
+ifndef V
+	QUIET_ASCIIDOC	= @echo '   ' ASCIIDOC $@;
+	QUIET_XMLTO	= @echo '   ' XMLTO $@;
+	QUIET_DB2TEXI	= @echo '   ' DB2TEXI $@;
+	QUIET_MAKEINFO	= @echo '   ' MAKEINFO $@;
+	QUIET_DBLATEX	= @echo '   ' DBLATEX $@;
+	QUIET_XSLTPROC	= @echo '   ' XSLTPROC $@;
+	QUIET_GEN	= @echo '   ' GEN $@;
+	QUIET_LINT	= @echo '   ' LINT $@;
+	QUIET_STDERR	= 2> /dev/null
+	QUIET_SUBDIR0	= +@subdir=
+	QUIET_SUBDIR1	= ;$(NO_SUBDIR) echo '   ' SUBDIR $$subdir; \
+			  $(MAKE) $(PRINT_DIR) -C $$subdir
+	export V
+endif
+endif
+
 all: html man
 
 html: $(DOC_HTML)
@@ -263,7 +284,7 @@ install-html: html
 ../GIT-VERSION-FILE: FORCE
 	$(QUIET_SUBDIR0)../ $(QUIET_SUBDIR1) GIT-VERSION-FILE
 
-ifneq ($(filter-out lint-docs clean,$(MAKECMDGOALS)),)
+ifneq ($(MAKECMDGOALS),clean)
 -include ../GIT-VERSION-FILE
 endif
 
@@ -304,12 +325,12 @@ $(mergetools_txt): mergetools-list.made
 
 mergetools-list.made: ../git-mergetool--lib.sh $(wildcard ../mergetools/*)
 	$(QUIET_GEN) \
-	$(SHELL_PATH) -c 'MERGE_TOOLS_DIR=../mergetools && TOOL_MODE=diff && \
+	$(SHELL_PATH) -c 'MERGE_TOOLS_DIR=../mergetools && \
 		. ../git-mergetool--lib.sh && \
-		show_tool_names can_diff' | sed -e "s/\([a-z0-9]*\)/\`\1\`;;/" >mergetools-diff.txt && \
-	$(SHELL_PATH) -c 'MERGE_TOOLS_DIR=../mergetools && TOOL_MODE=merge && \
+		show_tool_names can_diff "* " || :' >mergetools-diff.txt && \
+	$(SHELL_PATH) -c 'MERGE_TOOLS_DIR=../mergetools && \
 		. ../git-mergetool--lib.sh && \
-		show_tool_names can_merge' | sed -e "s/\([a-z0-9]*\)/\`\1\`;;/" >mergetools-merge.txt && \
+		show_tool_names can_merge "* " || :' >mergetools-merge.txt && \
 	date >$@
 
 TRACK_ASCIIDOCFLAGS = $(subst ','\'',$(ASCIIDOC_COMMON):$(ASCIIDOC_HTML):$(ASCIIDOC_DOCBOOK))
@@ -322,7 +343,6 @@ GIT-ASCIIDOCFLAGS: FORCE
             fi
 
 clean:
-	$(RM) -rf .build/
 	$(RM) *.xml *.xml+ *.html *.html+ *.1 *.5 *.7
 	$(RM) *.texi *.texi+ *.texi++ git.info gitman.info
 	$(RM) *.pdf
@@ -392,7 +412,7 @@ gitman.texi: $(MAN_XML) cat-texi.perl texi.xsl
 	$(RM) $@+
 
 gitman.info: gitman.texi
-	$(QUIET_MAKEINFO)$(MAKEINFO) --no-split --no-validate $<
+	$(QUIET_MAKEINFO)$(MAKEINFO) --no-split --no-validate $*.texi
 
 $(patsubst %.txt,%.texi,$(MAN_TXT)): %.texi : %.xml
 	$(QUIET_DB2TEXI)$(DOCBOOK2X_TEXI) --to-stdout $*.xml >$@
@@ -436,46 +456,21 @@ quick-install-html: require-htmlrepo
 print-man1:
 	@for i in $(MAN1_TXT); do echo $$i; done
 
-## Lint: gitlink
-LINT_DOCS_GITLINK = $(patsubst %.txt,.build/lint-docs/gitlink/%.ok,$(HOWTO_TXT) $(DOC_DEP_TXT))
-$(LINT_DOCS_GITLINK): lint-gitlink.perl
-$(LINT_DOCS_GITLINK): .build/lint-docs/gitlink/%.ok: %.txt
-	$(call mkdir_p_parent_template)
-	$(QUIET_LINT_GITLINK)$(PERL_PATH) lint-gitlink.perl \
-		$< \
+lint-docs::
+	$(QUIET_LINT)$(PERL_PATH) lint-gitlink.perl \
 		$(HOWTO_TXT) $(DOC_DEP_TXT) \
 		--section=1 $(MAN1_TXT) \
 		--section=5 $(MAN5_TXT) \
-		--section=7 $(MAN7_TXT) >$@
-.PHONY: lint-docs-gitlink
-lint-docs-gitlink: $(LINT_DOCS_GITLINK)
-
-## Lint: man-end-blurb
-LINT_DOCS_MAN_END_BLURB = $(patsubst %.txt,.build/lint-docs/man-end-blurb/%.ok,$(MAN_TXT))
-$(LINT_DOCS_MAN_END_BLURB): lint-man-end-blurb.perl
-$(LINT_DOCS_MAN_END_BLURB): .build/lint-docs/man-end-blurb/%.ok: %.txt
-	$(call mkdir_p_parent_template)
-	$(QUIET_LINT_MANEND)$(PERL_PATH) lint-man-end-blurb.perl $< >$@
-.PHONY: lint-docs-man-end-blurb
-
-## Lint: man-section-order
-LINT_DOCS_MAN_SECTION_ORDER = $(patsubst %.txt,.build/lint-docs/man-section-order/%.ok,$(MAN_TXT))
-$(LINT_DOCS_MAN_SECTION_ORDER): lint-man-section-order.perl
-$(LINT_DOCS_MAN_SECTION_ORDER): .build/lint-docs/man-section-order/%.ok: %.txt
-	$(call mkdir_p_parent_template)
-	$(QUIET_LINT_MANSEC)$(PERL_PATH) lint-man-section-order.perl $< >$@
-.PHONY: lint-docs-man-section-order
-lint-docs-man-section-order: $(LINT_DOCS_MAN_SECTION_ORDER)
-
-## Lint: list of targets above
-.PHONY: lint-docs
-lint-docs: lint-docs-gitlink
-lint-docs: lint-docs-man-end-blurb
-lint-docs: lint-docs-man-section-order
+		--section=7 $(MAN7_TXT); \
+	$(PERL_PATH) lint-man-end-blurb.perl $(MAN_TXT); \
+	$(PERL_PATH) lint-man-section-order.perl $(MAN_TXT);
 
 ifeq ($(wildcard po/Makefile),po/Makefile)
 doc-l10n install-l10n::
 	$(MAKE) -C po $@
 endif
 
+# Delete the target file on error
+.DELETE_ON_ERROR:
+
 .PHONY: FORCE

Documentation/MyFirstContribution.txt

@@ -710,104 +710,13 @@ dependencies. `prove` also makes the output nicer.
 Go ahead and commit this change, as well.
 
 [[ready-to-share]]
-== Getting Ready to Share: Anatomy of a Patch Series
+== Getting Ready to Share
 
 You may have noticed already that the Git project performs its code reviews via
 emailed patches, which are then applied by the maintainer when they are ready
-and approved by the community. The Git project does not accept contributions from
+and approved by the community. The Git project does not accept patches from
 pull requests, and the patches emailed for review need to be formatted a
-specific way.
-
-:patch-series: https://lore.kernel.org/git/pull.1218.git.git.1645209647.gitgitgadget@gmail.com/
-:lore: https://lore.kernel.org/git/
-
-Before taking a look at how to convert your commits into emailed patches,
-let's analyze what the end result, a "patch series", looks like. Here is an
-{patch-series}[example] of the summary view for a patch series on the web interface of
-the {lore}[Git mailing list archive]:
-
-----
-2022-02-18 18:40 [PATCH 0/3] libify reflog John Cai via GitGitGadget
-2022-02-18 18:40 ` [PATCH 1/3] reflog: libify delete reflog function and helpers John Cai via GitGitGadget
-2022-02-18 19:10   ` Ævar Arnfjörð Bjarmason [this message]
-2022-02-18 19:39     ` Taylor Blau
-2022-02-18 19:48       ` Ævar Arnfjörð Bjarmason
-2022-02-18 19:35   ` Taylor Blau
-2022-02-21  1:43     ` John Cai
-2022-02-21  1:50       ` Taylor Blau
-2022-02-23 19:50         ` John Cai
-2022-02-18 20:00   ` // other replies ellided
-2022-02-18 18:40 ` [PATCH 2/3] reflog: call reflog_delete from reflog.c John Cai via GitGitGadget
-2022-02-18 19:15   ` Ævar Arnfjörð Bjarmason
-2022-02-18 20:26     ` Junio C Hamano
-2022-02-18 18:40 ` [PATCH 3/3] stash: call reflog_delete from reflog.c John Cai via GitGitGadget
-2022-02-18 19:20   ` Ævar Arnfjörð Bjarmason
-2022-02-19  0:21     ` Taylor Blau
-2022-02-22  2:36     ` John Cai
-2022-02-22 10:51       ` Ævar Arnfjörð Bjarmason
-2022-02-18 19:29 ` [PATCH 0/3] libify reflog Ævar Arnfjörð Bjarmason
-2022-02-22 18:30 ` [PATCH v2 0/3] libify reflog John Cai via GitGitGadget
-2022-02-22 18:30   ` [PATCH v2 1/3] stash: add test to ensure reflog --rewrite --updatref behavior John Cai via GitGitGadget
-2022-02-23  8:54     ` Ævar Arnfjörð Bjarmason
-2022-02-23 21:27       ` Junio C Hamano
-// continued
-----
-
-We can note a few things:
-
-- Each commit is sent as a separate email, with the commit message title as
-  subject, prefixed with "[PATCH _i_/_n_]" for the _i_-th commit of an
-  _n_-commit series.
-- Each patch is sent as a reply to an introductory email called the _cover
-  letter_ of the series, prefixed "[PATCH 0/_n_]".
-- Subsequent iterations of the patch series are labelled "PATCH v2", "PATCH
-  v3", etc. in place of "PATCH". For example, "[PATCH v2 1/3]" would be the first of
-  three patches in the second iteration. Each iteration is sent with a new cover
-  letter (like "[PATCH v2 0/3]" above), itself a reply to the cover letter of the
-  previous iteration (more on that below).
-
-NOTE: A single-patch topic is sent with "[PATCH]", "[PATCH v2]", etc. without
-_i_/_n_ numbering (in the above thread overview, no single-patch topic appears,
-though).
-
-[[cover-letter]]
-=== The cover letter
-
-In addition to an email per patch, the Git community also expects your patches
-to come with a cover letter. This is an important component of change
-submission as it explains to the community from a high level what you're trying
-to do, and why, in a way that's more apparent than just looking at your
-patches.
-
-The title of your cover letter should be something which succinctly covers the
-purpose of your entire topic branch. It's often in the imperative mood, just
-like our commit message titles. Here is how we'll title our series:
-
----
-Add the 'psuh' command
----
-
-The body of the cover letter is used to give additional context to reviewers.
-Be sure to explain anything your patches don't make clear on their own, but
-remember that since the cover letter is not recorded in the commit history,
-anything that might be useful to future readers of the repository's history
-should also be in your commit messages.
-
-Here's an example body for `psuh`:
-
-----
-Our internal metrics indicate widespread interest in the command
-git-psuh - that is, many users are trying to use it, but finding it is
-unavailable, using some unknown workaround instead.
-
-The following handful of patches add the psuh command and implement some
-handy features on top of it.
-
-This patchset is part of the MyFirstContribution tutorial and should not
-be merged.
-----
-
-At this point the tutorial diverges, in order to demonstrate two
+specific way. At this point the tutorial diverges, in order to demonstrate two
 different methods of formatting your patchset and getting it reviewed.
 
 The first method to be covered is GitGitGadget, which is useful for those
@@ -899,22 +808,8 @@ https://github.com/gitgitgadget/git and open a PR either with the "New pull
 request" button or the convenient "Compare & pull request" button that may
 appear with the name of your newly pushed branch.
 
-Review the PR's title and description, as they're used by GitGitGadget
-respectively as the subject and body of the cover letter for your change. Refer
-to <<cover-letter,"The cover letter">> above for advice on how to title your
-submission and what content to include in the description.
-
-NOTE: For single-patch contributions, your commit message should already be
-meaningful and explain at a high level the purpose (what is happening and why)
-of your patch, so you usually do not need any additional context. In that case,
-remove the PR description that GitHub automatically generates from your commit
-message (your PR description should be empty). If you do need to supply even
-more context, you can do so in that space and it will be appended to the email
-that GitGitGadget will send, between the three-dash line and the diffstat
-(see <<single-patch,Bonus Chapter: One-Patch Changes>> for how this looks once
-submitted).
-
-When you're happy, submit your pull request.
+Review the PR's title and description, as it's used by GitGitGadget as the cover
+letter for your change. When you're happy, submit your pull request.
 
 [[run-ci-ggg]]
 === Running CI and Getting Ready to Send
@@ -1010,34 +905,19 @@ Sending emails with Git is a two-part process; before you can prepare the emails
 themselves, you'll need to prepare the patches. Luckily, this is pretty simple:
 
 ----
-$ git format-patch --cover-letter -o psuh/ --base=auto psuh@{u}..psuh
+$ git format-patch --cover-letter -o psuh/ master..psuh
 ----
 
- . The `--cover-letter` option tells `format-patch` to create a
-   cover letter template for you. You will need to fill in the
-   template before you're ready to send - but for now, the template
-   will be next to your other patches.
+The `--cover-letter` parameter tells `format-patch` to create a cover letter
+template for you. You will need to fill in the template before you're ready
+to send - but for now, the template will be next to your other patches.
 
- . The `-o psuh/` option tells `format-patch` to place the patch
-   files into a directory. This is useful because `git send-email`
-   can take a directory and send out all the patches from there.
+The `-o psuh/` parameter tells `format-patch` to place the patch files into a
+directory. This is useful because `git send-email` can take a directory and
+send out all the patches from there.
 
- . The `--base=auto` option tells the command to record the "base
-   commit", on which the recipient is expected to apply the patch
-   series.  The `auto` value will cause `format-patch` to compute
-   the base commit automatically, which is the merge base of tip
-   commit of the remote-tracking branch and the specified revision
-   range.
-
- . The `psuh@{u}..psuh` option tells `format-patch` to generate
-   patches for the commits you created on the `psuh` branch since it
-   forked from its upstream (which is `origin/master` if you
-   followed the example in the "Set up your workspace" section).  If
-   you are already on the `psuh` branch, you can just say `@{u}`,
-   which means "commits on the current branch since it forked from
-   its upstream", which is the same thing.
-
-The command will make one patch file per commit. After you
+`master..psuh` tells `format-patch` to generate patches for the difference
+between `master` and `psuh`. It will make one patch file per commit. After you
 run, you can go have a look at each of the patches with your favorite text
 editor and make sure everything looks alright; however, it's not recommended to
 make code fixups via the patch file. It's a better idea to make the change the
@@ -1057,29 +937,49 @@ but want reviewers to look at what they have so far. You can add this flag with
 Check and make sure that your patches and cover letter template exist in the
 directory you specified - you're nearly ready to send out your review!
 
-[[preparing-cover-letter]]
+[[cover-letter]]
 === Preparing Email
 
-Since you invoked `format-patch` with `--cover-letter`, you've already got a
-cover letter template ready. Open it up in your favorite editor.
+In addition to an email per patch, the Git community also expects your patches
+to come with a cover letter, typically with a subject line [PATCH 0/x] (where
+x is the number of patches you're sending). Since you invoked `format-patch`
+with `--cover-letter`, you've already got a template ready. Open it up in your
+favorite editor.
 
 You should see a number of headers present already. Check that your `From:`
-header is correct. Then modify your `Subject:` (see <<cover-letter,above>> for
-how to choose good title for your patch series):
+header is correct. Then modify your `Subject:` to something which succinctly
+covers the purpose of your entire topic branch, for example:
 
 ----
-Subject: [PATCH 0/7] Add the 'psuh' command
+Subject: [PATCH 0/7] adding the 'psuh' command
 ----
 
 Make sure you retain the ``[PATCH 0/X]'' part; that's what indicates to the Git
-community that this email is the beginning of a patch series, and many
-reviewers filter their email for this type of flag.
+community that this email is the beginning of a review, and many reviewers
+filter their email for this type of flag.
 
 You'll need to add some extra parameters when you invoke `git send-email` to add
 the cover letter.
 
-Next you'll have to fill out the body of your cover letter. Again, see
-<<cover-letter,above>> for what content to include.
+Next you'll have to fill out the body of your cover letter. This is an important
+component of change submission as it explains to the community from a high level
+what you're trying to do, and why, in a way that's more apparent than just
+looking at your diff. Be sure to explain anything your diff doesn't make clear
+on its own.
+
+Here's an example body for `psuh`:
+
+----
+Our internal metrics indicate widespread interest in the command
+git-psuh - that is, many users are trying to use it, but finding it is
+unavailable, using some unknown workaround instead.
+
+The following handful of patches add the psuh command and implement some
+handy features on top of it.
+
+This patchset is part of the MyFirstContribution tutorial and should not
+be merged.
+----
 
 The template created by `git format-patch --cover-letter` includes a diffstat.
 This gives reviewers a summary of what they're in for when reviewing your topic.
@@ -1129,42 +1029,22 @@ kidding - be patient!)
 [[v2-git-send-email]]
 === Sending v2
 
-This section will focus on how to send a v2 of your patchset. To learn what
-should go into v2, skip ahead to <<reviewing,Responding to Reviews>> for
-information on how to handle comments from reviewers.
+Skip ahead to <<reviewing,Responding to Reviews>> for information on how to
+handle comments from reviewers. Continue this section when your topic branch is
+shaped the way you want it to look for your patchset v2.
 
-We'll reuse our `psuh` topic branch for v2. Before we make any changes, we'll
-mark the tip of our v1 branch for easy reference:
+When you're ready with the next iteration of your patch, the process is fairly
+similar.
+
+First, generate your v2 patches again:
 
 ----
-$ git checkout psuh
-$ git branch psuh-v1
+$ git format-patch -v2 --cover-letter -o psuh/ master..psuh
 ----
 
-Refine your patch series by using `git rebase -i` to adjust commits based upon
-reviewer comments. Once the patch series is ready for submission, generate your
-patches again, but with some new flags:
-
-----
-$ git format-patch -v2 --cover-letter -o psuh/ --range-diff master..psuh-v1 master..
-----
-
-The `--range-diff master..psuh-v1` parameter tells `format-patch` to include a
-range-diff between `psuh-v1` and `psuh` in the cover letter (see
-linkgit:git-range-diff[1]). This helps tell reviewers about the differences
-between your v1 and v2 patches.
-
-The `-v2` parameter tells `format-patch` to output your patches
-as version "2". For instance, you may notice that your v2 patches are
-all named like `v2-000n-my-commit-subject.patch`. `-v2` will also format
-your patches by prefixing them with "[PATCH v2]" instead of "[PATCH]",
-and your range-diff will be prefaced with "Range-diff against v1".
-
-Afer you run this command, `format-patch` will output the patches to the `psuh/`
-directory, alongside the v1 patches. Using a single directory makes it easy to
-refer to the old v1 patches while proofreading the v2 patches, but you will need
-to be careful to send out only the v2 patches. We will use a pattern like
-"psuh/v2-*.patch" (not "psuh/*.patch", which would match v1 and v2 patches).
+This will add your v2 patches, all named like `v2-000n-my-commit-subject.patch`,
+to the `psuh/` directory. You may notice that they are sitting alongside the v1
+patches; that's fine, but be careful when you are ready to send them.
 
 Edit your cover letter again. Now is a good time to mention what's different
 between your last version and now, if it's something significant. You do not
@@ -1202,7 +1082,7 @@ to the command:
 ----
 $ git send-email --to=target@example.com
 		 --in-reply-to="<foo.12345.author@example.com>"
-		 psuh/v2-*.patch
+		 psuh/v2*
 ----
 
 [[single-patch]]

Documentation/MyFirstObjectWalk.txt

@@ -58,19 +58,14 @@ running, enable trace output by setting the environment variable `GIT_TRACE`.
 
 Add usage text and `-h` handling, like all subcommands should consistently do
 (our test suite will notice and complain if you fail to do so).
-We'll need to include the `parse-options.h` header.
 
 ----
-#include "parse-options.h"
-
-...
-
 int cmd_walken(int argc, const char **argv, const char *prefix)
 {
 	const char * const walken_usage[] = {
 		N_("git walken"),
 		NULL,
-	};
+	}
 	struct option options[] = {
 		OPT_END()
 	};
@@ -200,14 +195,9 @@ Similarly to the default values, we don't have anything to do here yet
 ourselves; however, we should call `git_default_config()` if we aren't calling
 any other existing config callbacks.
 
-Add a new function to `builtin/walken.c`.
-We'll also need to include the `config.h` header:
+Add a new function to `builtin/walken.c`:
 
 ----
-#include "config.h"
-
-...
-
 static int git_walken_config(const char *var, const char *value, void *cb)
 {
 	/*
@@ -239,14 +229,8 @@ typically done by calling `repo_init_revisions()` with the repository you intend
 to target, as well as the `prefix` argument of `cmd_walken` and your `rev_info`
 struct.
 
-Add the `struct rev_info` and the `repo_init_revisions()` call.
-We'll also need to include the `revision.h` header:
-
+Add the `struct rev_info` and the `repo_init_revisions()` call:
 ----
-#include "revision.h"
-
-...
-
 int cmd_walken(int argc, const char **argv, const char *prefix)
 {
 	/* This can go wherever you like in your declarations.*/
@@ -522,25 +506,24 @@ function shows that the all-object walk is being performed by
 `traverse_commit_list()` or `traverse_commit_list_filtered()`. Those two
 functions reside in `list-objects.c`; examining the source shows that, despite
 the name, these functions traverse all kinds of objects. Let's have a look at
-the arguments to `traverse_commit_list()`.
+the arguments to `traverse_commit_list_filtered()`, which are a superset of the
+arguments to the unfiltered version.
 
-- `struct rev_info *revs`: This is the `rev_info` used for the walk. If
-  its `filter` member is not `NULL`, then `filter` contains information for
-  how to filter the object list.
+- `struct list_objects_filter_options *filter_options`: This is a struct which
+  stores a filter-spec as outlined in `Documentation/rev-list-options.txt`.
+- `struct rev_info *revs`: This is the `rev_info` used for the walk.
 - `show_commit_fn show_commit`: A callback which will be used to handle each
   individual commit object.
 - `show_object_fn show_object`: A callback which will be used to handle each
   non-commit object (so each blob, tree, or tag).
 - `void *show_data`: A context buffer which is passed in turn to `show_commit`
   and `show_object`.
-
-In addition, `traverse_commit_list_filtered()` has an additional paramter:
-
 - `struct oidset *omitted`: A linked-list of object IDs which the provided
   filter caused to be omitted.
 
-It looks like these methods use callbacks we provide instead of needing us
-to call it repeatedly ourselves. Cool! Let's add the callbacks first.
+It looks like this `traverse_commit_list_filtered()` uses callbacks we provide
+instead of needing us to call it repeatedly ourselves. Cool! Let's add the
+callbacks first.
 
 For the sake of this tutorial, we'll simply keep track of how many of each kind
 of object we find. At file scope in `builtin/walken.c` add the following
@@ -641,14 +624,9 @@ static void walken_object_walk(struct rev_info *rev)
 ----
 
 Let's start by calling just the unfiltered walk and reporting our counts.
-Complete your implementation of `walken_object_walk()`.
-We'll also need to include the `list-objects.h` header.
+Complete your implementation of `walken_object_walk()`:
 
 ----
-#include "list-objects.h"
-
-...
-
 	traverse_commit_list(rev, walken_show_commit, walken_show_object, NULL);
 
 	printf("commits %d\nblobs %d\ntags %d\ntrees %d\n", commit_count,
@@ -713,9 +691,20 @@ help understand. In our case, that means we omit trees and blobs not directly
 referenced by `HEAD` or `HEAD`'s history, because we begin the walk with only
 `HEAD` in the `pending` list.)
 
+First, we'll need to `#include "list-objects-filter-options.h"` and set up the
+`struct list_objects_filter_options` at the top of the function.
+
+----
+static void walken_object_walk(struct rev_info *rev)
+{
+	struct list_objects_filter_options filter_options = {};
+
+	...
+----
+
 For now, we are not going to track the omitted objects, so we'll replace those
 parameters with `NULL`. For the sake of simplicity, we'll add a simple
-build-time branch to use our filter or not. Preface the line calling
+build-time branch to use our filter or not. Replace the line calling
 `traverse_commit_list()` with the following, which will remind us which kind of
 walk we've just performed:
 
@@ -723,17 +712,19 @@ walk we've just performed:
 	if (0) {
 		/* Unfiltered: */
 		trace_printf(_("Unfiltered object walk.\n"));
+		traverse_commit_list(rev, walken_show_commit,
+				walken_show_object, NULL);
 	} else {
 		trace_printf(
 			_("Filtered object walk with filterspec 'tree:1'.\n"));
-		CALLOC_ARRAY(rev->filter, 1);
-		parse_list_objects_filter(rev->filter, "tree:1");
+		parse_list_objects_filter(&filter_options, "tree:1");
+
+		traverse_commit_list_filtered(&filter_options, rev,
+			walken_show_commit, walken_show_object, NULL, NULL);
 	}
-	traverse_commit_list(rev, walken_show_commit,
-			     walken_show_object, NULL);
 ----
 
-The `rev->filter` member is usually built directly from a command
+`struct list_objects_filter_options` is usually built directly from a command
 line argument, so the module provides an easy way to build one from a string.
 Even though we aren't taking user input right now, we can still build one with
 a hardcoded string using `parse_list_objects_filter()`.
@@ -772,7 +763,7 @@ object:
 ----
 	...
 
-		traverse_commit_list_filtered(rev,
+		traverse_commit_list_filtered(&filter_options, rev,
 			walken_show_commit, walken_show_object, NULL, &omitted);
 
 	...

Documentation/RelNotes/2.30.5.txt

@@ -0,0 +1,12 @@
+Git v2.30.5 Release Notes
+=========================
+
+This release contains minor fix-ups for the changes that went into
+Git 2.30.3 and 2.30.4, addressing CVE-2022-29187.
+
+ * The safety check that verifies a safe ownership of the Git
+   worktree is now extended to also cover the ownership of the Git
+   directory (and the `.git` file, if there is any).
+
+Carlo Marcelo Arenas Belón (1):
+      setup: tighten ownership checks post CVE-2022-24765

Documentation/RelNotes/2.30.6.txt

@@ -0,0 +1,60 @@
+Git v2.30.6 Release Notes
+=========================
+
+This release addresses the security issues CVE-2022-39253 and
+CVE-2022-39260.
+
+Fixes since v2.30.5
+-------------------
+
+ * CVE-2022-39253:
+   When relying on the `--local` clone optimization, Git dereferences
+   symbolic links in the source repository before creating hardlinks
+   (or copies) of the dereferenced link in the destination repository.
+   This can lead to surprising behavior where arbitrary files are
+   present in a repository's `$GIT_DIR` when cloning from a malicious
+   repository.
+
+   Git will no longer dereference symbolic links via the `--local`
+   clone mechanism, and will instead refuse to clone repositories that
+   have symbolic links present in the `$GIT_DIR/objects` directory.
+
+   Additionally, the value of `protocol.file.allow` is changed to be
+   "user" by default.
+
+ * CVE-2022-39260:
+   An overly-long command string given to `git shell` can result in
+   overflow in `split_cmdline()`, leading to arbitrary heap writes and
+   remote code execution when `git shell` is exposed and the directory
+   `$HOME/git-shell-commands` exists.
+
+   `git shell` is taught to refuse interactive commands that are
+   longer than 4MiB in size. `split_cmdline()` is hardened to reject
+   inputs larger than 2GiB.
+
+Credit for finding CVE-2022-39253 goes to Cory Snider of Mirantis. The
+fix was authored by Taylor Blau, with help from Johannes Schindelin.
+
+Credit for finding CVE-2022-39260 goes to Kevin Backhouse of GitHub.
+The fix was authored by Kevin Backhouse, Jeff King, and Taylor Blau.
+
+
+Jeff King (2):
+      shell: add basic tests
+      shell: limit size of interactive commands
+
+Kevin Backhouse (1):
+      alias.c: reject too-long cmdline strings in split_cmdline()
+
+Taylor Blau (11):
+      builtin/clone.c: disallow `--local` clones with symlinks
+      t/lib-submodule-update.sh: allow local submodules
+      t/t1NNN: allow local submodules
+      t/2NNNN: allow local submodules
+      t/t3NNN: allow local submodules
+      t/t4NNN: allow local submodules
+      t/t5NNN: allow local submodules
+      t/t6NNN: allow local submodules
+      t/t7NNN: allow local submodules
+      t/t9NNN: allow local submodules
+      transport: make `protocol.file.allow` be "user" by default

Documentation/RelNotes/2.31.4.txt

@@ -0,0 +1,6 @@
+Git v2.31.4 Release Notes
+=========================
+
+This release merges up the fixes that appear in v2.30.5 to address
+the security issue CVE-2022-29187; see the release notes for that
+version for details.

Documentation/RelNotes/2.31.5.txt

@@ -0,0 +1,5 @@
+Git v2.31.5 Release Notes
+=========================
+
+This release merges the security fix that appears in v2.30.6; see
+the release notes for that version for details.

Documentation/RelNotes/2.32.3.txt

@@ -0,0 +1,6 @@
+Git v2.32.3 Release Notes
+=========================
+
+This release merges up the fixes that appear in v2.30.5 and
+v2.31.4 to address the security issue CVE-2022-29187; see the
+release notes for these versions for details.

Documentation/RelNotes/2.32.4.txt

@@ -0,0 +1,5 @@
+Git v2.32.4 Release Notes
+=========================
+
+This release merges the security fix that appears in v2.30.6; see
+the release notes for that version for details.

Documentation/RelNotes/2.33.4.txt

@@ -0,0 +1,6 @@
+Git v2.33.4 Release Notes
+=========================
+
+This release merges up the fixes that appear in v2.30.5, v2.31.4
+and v2.32.3 to address the security issue CVE-2022-29187; see
+the release notes for these versions for details.

Documentation/RelNotes/2.33.5.txt

@@ -0,0 +1,5 @@
+Git v2.33.5 Release Notes
+=========================
+
+This release merges the security fix that appears in v2.30.6; see
+the release notes for that version for details.

Documentation/RelNotes/2.34.0.txt

@@ -1,438 +0,0 @@
-Git 2.34 Release Notes
-======================
-
-Updates since Git 2.33
-----------------------
-
-Backward compatibility notes
-
- * The "--preserve-merges" option of "git rebase" has been removed.
-
-
-UI, Workflows & Features
-
- * Pathname expansion (like "~username/") learned a way to specify a
-   location relative to Git installation (e.g. its $sharedir which is
-   $(prefix)/share), with "%(prefix)".
-
- * The `ort` strategy is used instead of `recursive` as the default
-   merge strategy.
-
- * The userdiff pattern for "java" language has been updated.
-
- * "git rebase" by default skips changes that are equivalent to
-   commits that are already in the history the branch is rebased onto;
-   give messages when this happens to let the users be aware of
-   skipped commits, and also teach them how to tell "rebase" to keep
-   duplicated changes.
-
- * The advice message that "git cherry-pick" gives when it asks
-   conflicted replay of a commit to be resolved by the end user has
-   been updated.
-
- * After "git clone --recurse-submodules", all submodules are cloned
-   but they are not by default recursed into by other commands.  With
-   submodule.stickyRecursiveClone configuration set, submodule.recurse
-   configuration is set to true in a repository created by "clone"
-   with "--recurse-submodules" option.
-
- * The logic for auto-correction of misspelt subcommands learned to go
-   interactive when the help.autocorrect configuration variable is set
-   to 'prompt'.
-
- * "git maintenance" scheduler learned to use systemd timers as a
-   possible backend.
-
- * "git diff --submodule=diff" showed failure from run_command() when
-   trying to run diff inside a submodule, when the user manually
-   removes the submodule directory.
-
- * "git bundle unbundle" learned to show progress display.
-
- * In cone mode, the sparse-index code path learned to remove ignored
-   files (like build artifacts) outside the sparse cone, allowing the
-   entire directory outside the sparse cone to be removed, which is
-   especially useful when the sparse patterns change.
-
- * Taking advantage of the CGI interface, http-backend has been
-   updated to enable protocol v2 automatically when the other side
-   asks for it.
-
- * The credential-cache helper has been adjusted to Windows.
-
- * The error in "git help no-such-git-command" is handled better.
-
- * The unicode character width table (used for output alignment) has
-   been updated.
-
- * The ref iteration code used to optionally allow dangling refs to be
-   shown, which has been tightened up.
-
- * "git add", "git mv", and "git rm" have been adjusted to avoid
-   updating paths outside of the sparse-checkout definition unless
-   the user specifies a "--sparse" option.
-
- * "git repack" has been taught to generate multi-pack reachability
-   bitmaps.
-
- * "git fsck" has been taught to report mismatch between expected and
-   actual types of an object better.
-
- * In addition to GnuPG, ssh public crypto can be used for object and
-   push-cert signing.  Note that this feature cannot be used with
-   ssh-keygen from OpenSSH 8.7, whose support for it is broken.  Avoid
-   using it unless you update to OpenSSH 8.8.
-
- * "git log --grep=string --author=name" learns to highlight hits just
-   like "git grep string" does.
-
-
-
-Performance, Internal Implementation, Development Support etc.
-
- * "git bisect" spawned "git show-branch" only to pretty-print the
-   title of the commit after checking out the next version to be
-   tested; this has been rewritten in C.
-
- * "git add" can work better with the sparse index.
-
- * Support for ancient versions of cURL library (pre 7.19.4) has been
-   dropped.
-
- * A handful of tests that assumed implementation details of files
-   backend for refs have been cleaned up.
-
- * trace2 logs learned to show parent process name to see in what
-   context Git was invoked.
-
- * Loading of ref tips to prepare for common ancestry negotiation in
-   "git fetch-pack" has been optimized by taking advantage of the
-   commit graph when available.
-
- * Remind developers that the userdiff patterns should be kept simple
-   and permissive, assuming that the contents they apply are always
-   syntactically correct.
-
- * The current implementation of GIT_TEST_FAIL_PREREQS is broken in
-   that checking for the lack of a prerequisite would not work.  Avoid
-   the use of "if ! test_have_prereq X" in a test script.
-
- * The revision traversal API has been optimized by taking advantage
-   of the commit-graph, when available, to determine if a commit is
-   reachable from any of the existing refs.
-
- * "git fetch --quiet" optimization to avoid useless computation of
-   info that will never be displayed.
-
- * Callers from older advice_config[] based API has been updated to
-   use the newer advice_if_enabled() and advice_enabled() API.
-
- * Teach "test_pause" and "debug" helpers to allow using the HOME and
-   TERM environment variables the user usually uses.
-
- * "make INSTALL_STRIP=-s install" allows the installation step to use
-   "install -s" to strip the binaries as they get installed.
-
- * Code that handles large number of refs in the "git fetch" code
-   path has been optimized.
-
- * The reachability bitmap file used to be generated only for a single
-   pack, but now we've learned to generate bitmaps for history that
-   span across multiple packfiles.
-
- * The code to make "git grep" recurse into submodules has been
-   updated to migrate away from the "add submodule's object store as
-   an alternate object store" mechanism (which is suboptimal).
-
- * The tracing of process ancestry information has been enhanced.
-
- * Reduce number of write(2) system calls while sending the
-   ref advertisement.
-
- * Update the build procedure to use the "-pedantic" build when
-   DEVELOPER makefile macro is in effect.
-
- * Large part of "git submodule add" gets rewritten in C.
-
- * The run-command API has been updated so that the callers can easily
-   ask the file descriptors open for packfiles to be closed immediately
-   before spawning commands that may trigger auto-gc.
-
- * An oddball OPTION_ARGUMENT feature has been removed from the
-   parse-options API.
-
- * The mergesort implementation used to sort linked list has been
-   optimized.
-
- * Remove external declaration of functions that no longer exist.
-
- * "git multi-pack-index write --bitmap" learns to propagate the
-   hashcache from original bitmap to resulting bitmap.
-
- * CI learns to run the leak sanitizer builds.
-
- * "git grep --recurse-submodules" takes trees and blobs from the
-   submodule repository, but the textconv settings when processing a
-   blob from the submodule is not taken from the submodule repository.
-   A test is added to demonstrate the issue, without fixing it.
-
- * Teach "git help -c" into helping the command line completion of
-   configuration variables.
-
- * When "git cmd -h" shows more than one line of usage text (e.g.
-   the cmd subcommand may take sub-sub-command), parse-options API
-   learned to align these lines, even across i18n/l10n.
-
- * Prevent "make sparse" from running for the source files that
-   haven't been modified.
-
- * The code path to write a new version of .midx multi-pack index files
-   has learned to release the mmaped memory holding the current
-   version of .midx before removing them from the disk, as some
-   platforms do not allow removal of a file that still has mapping.
-
- * A new feature has been added to abort early in the test framework.
-
-
-Fixes since v2.33
------------------
-
- * Input validation of "git pack-objects --stdin-packs" has been
-   corrected.
-
- * Bugfix for common ancestor negotiation recently introduced in "git
-   push" code path.
-
- * "git pull" had various corner cases that were not well thought out
-   around its --rebase backend, e.g. "git pull --ff-only" did not stop
-   but went ahead and rebased when the history on other side is not a
-   descendant of our history.  The series tries to fix them up.
-
- * "git apply" miscounted the bytes and failed to read to the end of
-   binary hunks.
-
- * "git range-diff" code clean-up.
-
- * "git commit --fixup" now works with "--edit" again, after it was
-   broken in v2.32.
-
- * Use upload-artifacts v1 (instead of v2) for 32-bit linux, as the
-   new version has a blocker bug for that architecture.
-
- * Checking out all the paths from HEAD during the last conflicted
-   step in "git rebase" and continuing would cause the step to be
-   skipped (which is expected), but leaves MERGE_MSG file behind in
-   $GIT_DIR and confuses the next "git commit", which has been
-   corrected.
-
- * Various bugs in "git rebase -r" have been fixed.
-
- * mmap() imitation used to call xmalloc() that dies upon malloc()
-   failure, which has been corrected to just return an error to the
-   caller to be handled.
-
- * "git diff --relative" segfaulted and/or produced incorrect result
-   when there are unmerged paths.
-
- * The delayed checkout code path in "git checkout" etc. were chatty
-   even when --quiet and/or --no-progress options were given.
-
- * "git branch -D <branch>" used to refuse to remove a broken branch
-   ref that points at a missing commit, which has been corrected.
-
- * Build update for Apple clang.
-
- * The parser for the "--nl" option of "git column" has been
-   corrected.
-
- * "git upload-pack" which runs on the other side of "git fetch"
-   forgot to take the ref namespaces into account when handling
-   want-ref requests.
-
- * The sparse-index support can corrupt the index structure by storing
-   a stale and/or uninitialized data, which has been corrected.
-
- * Buggy tests could damage repositories outside the throw-away test
-   area we created.  We now by default export GIT_CEILING_DIRECTORIES
-   to limit the damage from such a stray test.
-
- * Even when running "git send-email" without its own threaded
-   discussion support, a threading related header in one message is
-   carried over to the subsequent message to result in an unwanted
-   threading, which has been corrected.
-
- * The output from "git fast-export", when its anonymization feature
-   is in use, showed an annotated tag incorrectly.
-
- * Recent "diff -m" changes broke "gitk", which has been corrected.
-
- * The "git apply -3" code path learned not to bother the lower level
-   merge machinery when the three-way merge can be trivially resolved
-   without the content level merge.  This fixes a regression caused by
-   recent "-3way first and fall back to direct application" change.
-
- * The code that optionally creates the *.rev reverse index file has
-   been optimized to avoid needless computation when it is not writing
-   the file out.
-
- * "git range-diff -I... <range> <range>" segfaulted, which has been
-   corrected.
-
- * The order in which various files that make up a single (conceptual)
-   packfile has been reevaluated and straightened up.  This matters in
-   correctness, as an incomplete set of files must not be shown to a
-   running Git.
-
- * The "mode" word is useless in a call to open(2) that does not
-   create a new file.  Such a call in the files backend of the ref
-   subsystem has been cleaned up.
-
- * "git update-ref --stdin" failed to flush its output as needed,
-   which potentially led the conversation to a deadlock.
-
- * When "git am --abort" fails to abort correctly, it still exited
-   with exit status of 0, which has been corrected.
-
- * Correct nr and alloc members of strvec struct to be of type size_t.
-
- * "git stash", where the tentative change involves changing a
-   directory to a file (or vice versa), was confused, which has been
-   corrected.
-
- * "git clone" from a repository whose HEAD is unborn into a bare
-   repository didn't follow the branch name the other side used, which
-   is corrected.
-
- * "git cvsserver" had a long-standing bug in its authentication code,
-   which has finally been corrected (it is unclear and is a separate
-   question if anybody is seriously using it, though).
-
- * "git difftool --dir-diff" mishandled symbolic links.
-
- * Sensitive data in the HTTP trace were supposed to be redacted, but
-   we failed to do so in HTTP/2 requests.
-
- * "make clean" has been updated to remove leftover .depend/
-   directories, even when it is not told to use them to compute header
-   dependencies.
-
- * Protocol v0 clients can get stuck parsing a malformed feature line.
-
- * A few kinds of changes "git status" can show were not documented.
-   (merge d2a534c515 ja/doc-status-types-and-copies later to maint).
-
- * The mergesort implementation used to sort linked list has been
-   optimized.
-   (merge c90cfc225b rs/mergesort later to maint).
-
- * An editor session launched during a Git operation (e.g. during 'git
-   commit') can leave the terminal in a funny state.  The code path
-   has updated to save the terminal state before, and restore it
-   after, it spawns an editor.
-   (merge 3d411afabc cm/save-restore-terminal later to maint).
-
- * "git cat-file --batch" with the "--batch-all-objects" option is
-   supposed to iterate over all the objects found in a repository, but
-   it used to translate these object names using the replace mechanism,
-   which defeats the point of enumerating all objects in the repository.
-   This has been corrected.
-   (merge bf972896d7 jk/cat-file-batch-all-wo-replace later to maint).
-
- * Recent sparse-index work broke safety against attempts to add paths
-   with trailing slashes to the index, which has been corrected.
-   (merge c8ad9d04c6 rs/make-verify-path-really-verify-again later to maint).
-
- * The "--color-lines" and "--color-by-age" options of "git blame"
-   have been missing, which are now documented.
-   (merge 8c32856133 bs/doc-blame-color-lines later to maint).
-
- * The PATH used in CI job may be too wide and let incompatible dlls
-   to be grabbed, which can cause the build&test to fail.  Tighten it.
-   (merge 7491ef6198 js/windows-ci-path-fix later to maint).
-
- * Avoid performance measurements from getting ruined by gc and other
-   housekeeping pauses interfering in the middle.
-   (merge be79131a53 rs/disable-gc-during-perf-tests later to maint).
-
- * Stop "git add --dry-run" from creating new blob and tree objects.
-   (merge e578d0311d rs/add-dry-run-without-objects later to maint).
-
- * "git commit" gave duplicated error message when the object store
-   was unwritable, which has been corrected.
-   (merge 4ef91a2d79 ab/fix-commit-error-message-upon-unwritable-object-store later to maint).
-
- * Recent sparse-index addition, namely any use of index_name_pos(),
-   can expand sparse index entries and breaks any code that walks
-   cache-tree or existing index entries.  One such instance of such a
-   breakage has been corrected.
-
- * The xxdiff difftool backend can exit with status 128, which the
-   difftool-helper that launches the backend takes as a significant
-   failure, when it is not significant at all.  Work it around.
-   (merge 571f4348dd da/mergetools-special-case-xxdiff-exit-128 later to maint).
-
- * Improve test framework around unwritable directories.
-   (merge 5d22e18965 ab/test-cleanly-recreate-trash-directory later to maint).
-
- * "git push" client talking to an HTTP server did not diagnose the
-   lack of the final status report from the other side correctly,
-   which has been corrected.
-   (merge c5c3486f38 jk/http-push-status-fix later to maint).
-
- * Update "git archive" documentation and give explicit mention on the
-   compression level for both zip and tar.gz format.
-   (merge c4b208c309 bs/archive-doc-compression-level later to maint).
-
- * Drop "git sparse-checkout" from the list of common commands.
-   (merge 6a9a50a8af sg/sparse-index-not-that-common-a-command later to maint).
-
- * "git branch -c/-m new old" was not described to copy config, which
-   has been corrected.
-   (merge 8252ec300e jc/branch-copy-doc later to maint).
-
- * Squelch over-eager warning message added during this cycle.
-
- * Fix long-standing shell syntax error in the completion script.
-   (merge 46b0585286 re/completion-fix-test-equality later to maint).
-
- * Teach "git commit-graph" command not to allow using replace objects
-   at all, as we do not use the commit-graph at runtime when we see
-   object replacement.
-   (merge 095d112f8c ab/ignore-replace-while-working-on-commit-graph later to maint).
-
- * "git pull --no-verify" did not affect the underlying "git merge".
-   (merge 47bfdfb3fd ar/fix-git-pull-no-verify later to maint).
-
- * One CI task based on Fedora image noticed a not-quite-kosher
-   construct recently, which has been corrected.
-
- * "git pull --ff-only" and "git pull --rebase --ff-only" should make
-   it a no-op to attempt pulling from a remote that is behind us, but
-   instead the command errored out by saying it was impossible to
-   fast-forward, which may technically be true, but not a useful thing
-   to diagnose as an error.  This has been corrected.
-   (merge 361cb52383 jc/fix-pull-ff-only-when-already-up-to-date later to maint).
-
- * The way Cygwin emulates a unix-domain socket, on top of which the
-   simple-ipc mechanism is implemented, can race with the program on
-   the other side that wants to use the socket, and briefly make it
-   appear as a regular file before lstat(2) starts reporting it as a
-   socket.  We now have a workaround on the side that connects to a
-   unix domain socket.
-
- * Other code cleanup, docfix, build fix, etc.
-   (merge f188160be9 ab/bundle-remove-verbose-option later to maint).
-   (merge 8c6b4332b4 rs/close-pack-leakfix later to maint).
-   (merge 51b04c05b7 bs/difftool-msg-tweak later to maint).
-   (merge dd20e4a6db ab/make-compdb-fix later to maint).
-   (merge 6ffb990dc4 os/status-docfix later to maint).
-   (merge 100c2da2d3 rs/p3400-lose-tac later to maint).
-   (merge 76f3b69896 tb/aggregate-ignore-leading-whitespaces later to maint).
-   (merge 6e4fd8bfcd tz/doc-link-to-bundle-format-fix later to maint).
-   (merge f6c013dfa1 jc/doc-commit-header-continuation-line later to maint).
-   (merge ec9a37d69b ab/pkt-line-cleanup later to maint).
-   (merge 8650c6298c ab/fix-make-lint-docs later to maint).
-   (merge 1c720357ce ab/test-lib-diff-cleanup later to maint).
-   (merge 6b615dbece ks/submodule-add-message-fix later to maint).
-   (merge 203eb8381a jc/doc-format-patch-clarify-auto-base later to maint).
-   (merge 559664c792 ab/test-lib later to maint).

Documentation/RelNotes/2.34.1.txt

@@ -1,23 +0,0 @@
-Git v2.34.1 Release Notes
-=========================
-
-This release is primarily to fix a handful of regressions in Git 2.34.
-
-Fixes since v2.34
------------------
-
- * "git grep" looking in a blob that has non-UTF8 payload was
-   completely broken when linked with certain versions of PCREv2
-   library in the latest release.
-
- * "git pull" with any strategy when the other side is behind us
-   should succeed as it is a no-op, but doesn't.
-
- * An earlier change in 2.34.0 caused JGit application (that abused
-   GIT_EDITOR mechanism when invoking "git config") to get stuck with
-   a SIGTTOU signal; it has been reverted.
-
- * An earlier change that broke .gitignore matching has been reverted.
-
- * SubmittingPatches document gained a syntactically incorrect mark-up,
-   which has been corrected.

Documentation/RelNotes/2.34.2.txt

@@ -1,6 +0,0 @@
-Git v2.34.2 Release Notes
-=========================
-
-This release merges up the fixes that appear in v2.30.3, v2.31.2,
-v2.32.1 and v2.33.2 to address the security issue CVE-2022-24765;
-see the release notes for these versions for details.

Documentation/RelNotes/2.34.3.txt

@@ -1,4 +0,0 @@
-Git Documentation/RelNotes/2.34.3.txt Release Notes
-=========================
-
-This release merges up the fixes that appear in v2.34.3.

Documentation/RelNotes/2.35.0.txt

@@ -1,412 +0,0 @@
-Git 2.35 Release Notes
-======================
-
-Updates since Git 2.34
-----------------------
-
-Backward compatibility warts
-
- * "_" is now treated as any other URL-valid characters in an URL when
-   matching the per-URL configuration variable names.
-
- * The color palette used by "git grep" has been updated to match that
-   of GNU grep.
-
-
-Note to those who build from the source
-
- * You may need to define NO_UNCOMPRESS2 Makefile macro if you build
-   with zlib older than 1.2.9.
-
- * If your compiler cannot grok C99, the build will fail.  See the
-   instruction at the beginning of git-compat-util.h if this happens
-   to you.
-
-
-UI, Workflows & Features
-
- * "git status --porcelain=v2" now show the number of stash entries
-   with --show-stash like the normal output does.
-
- * "git stash" learned the "--staged" option to stash away what has
-   been added to the index (and nothing else).
-
- * "git var GIT_DEFAULT_BRANCH" is a way to see what name is used for
-   the newly created branch if "git init" is run.
-
- * Various operating modes of "git reset" have been made to work
-   better with the sparse index.
-
- * "git submodule deinit" for a submodule whose .git metadata
-   directory is embedded in its working tree refused to work, until
-   the submodule gets converted to use the "absorbed" form where the
-   metadata directory is stored in superproject, and a gitfile at the
-   top-level of the working tree of the submodule points at it.  The
-   command is taught to convert such submodules to the absorbed form
-   as needed.
-
- * The completion script (in contrib/) learns that the "--date"
-   option of commands from the "git log" family takes "human" and
-   "auto" as valid values.
-
- * "Zealous diff3" style of merge conflict presentation has been added.
-
- * The "git log --format=%(describe)" placeholder has been extended to
-   allow passing selected command-line options to the underlying "git
-   describe" command.
-
- * "default" and "reset" have been added to our color palette.
-
- * The cryptographic signing using ssh keys can specify literal keys
-   for keytypes whose name do not begin with the "ssh-" prefix by
-   using the "key::" prefix mechanism (e.g. "key::ecdsa-sha2-nistp256").
-
- * "git fetch" without the "--update-head-ok" option ought to protect
-   a checked out branch from getting updated, to prevent the working
-   tree that checks it out to go out of sync.  The code was written
-   before the use of "git worktree" got widespread, and only checked
-   the branch that was checked out in the current worktree, which has
-   been updated.
-
- * "git name-rev" has been tweaked to give output that is shorter and
-   easier to understand.
-
- * "git apply" has been taught to ignore a message without a patch
-   with the "--allow-empty" option.  It also learned to honor the
-   "--quiet" option given from the command line.
-
- * The "init" and "set" subcommands in "git sparse-checkout" have been
-   unified for a better user experience and performance.
-
- * Many git commands that deal with working tree files try to remove a
-   directory that becomes empty (i.e. "git switch" from a branch that
-   has the directory to another branch that does not would attempt
-   remove all files in the directory and the directory itself).  This
-   drops users into an unfamiliar situation if the command was run in
-   a subdirectory that becomes subject to removal due to the command.
-   The commands have been taught to keep an empty directory if it is
-   the directory they were started in to avoid surprising users.
-
- * "git am" learns "--empty=(stop|drop|keep)" option to tweak what is
-   done to a piece of e-mail without a patch in it.
-
- * The default merge message prepared by "git merge" records the name
-   of the current branch; the name can be overridden with a new option
-   to allow users to pretend a merge is made on a different branch.
-
- * The way "git p4" shows file sizes in its output has been updated to
-   use human-readable units.
-
- * "git -c branch.autosetupmerge=inherit branch new old" makes "new"
-   to have the same upstream as the "old" branch, instead of marking
-   "old" itself as its upstream.
-
-
-Performance, Internal Implementation, Development Support etc.
-
- * The use of errno as a means to carry the nature of error in the ref
-   API implementation has been reworked and reduced.
-
- * Teach and encourage first-time contributors to this project to
-   state the base commit when they submit their topic.
-
- * The command line completion for "git send-email" options have been
-   tweaked to make it easier to keep it in sync with the command itself.
-
- * Ensure that the sparseness of the in-core index matches the
-   index.sparse configuration specified by the repository immediately
-   after the on-disk index file is read.
-
- * Code clean-up to eventually allow information on remotes defined
-   for an arbitrary repository to be read.
-
- * Build optimization.
-
- * Tighten code for testing pack-bitmap.
-
- * Weather balloon to break people with compilers that do not support
-   C99.
-
- * The "reftable" backend for the refs API, without integrating into
-   the refs subsystem, has been added.
-
- * More tests are marked as leak-free.
-
- * The test framework learns to list unsatisfied test prerequisites,
-   and optionally error out when prerequisites that are expected to be
-   satisfied are not.
-
- * The default setting for trace2 event nesting was too low to cause
-   test failures, which is worked around by bumping it up in the test
-   framework.
-
- * Drop support for TravisCI and update test workflows at GitHub.
-
- * Many tests that used to need GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME
-   mechanism to force "git" to use 'master' as the default name for
-   the initial branch no longer need it; the use of the mechanism from
-   them have been removed.
-
- * Allow running our tests while disabling fsync.
-
- * Document the parameters given to the reflog entry iterator callback
-   functions.
-   (merge e6e94f34b2 jc/reflog-iterator-callback-doc later to maint).
-
- * The test helper for refs subsystem learned to write bogus and/or
-   nonexistent object name to refs to simulate error situations we
-   want to test Git in.
-
- * "diff --histogram" optimization.
-
- * Weather balloon to find compilers that do not grok variable
-   declaration in the for() loop.
-
- * diff and blame commands have been taught to work better with sparse
-   index.
-
- * The chainlint test script linter in the test suite has been updated.
-
- * The DEVELOPER=yes build uses -std=gnu99 now.
-
- * "git format-patch" uses a single rev_info instance and then exits.
-   Mark the structure with UNLEAK() macro to squelch leak sanitizer.
-
- * New interface into the tmp-objdir API to help in-core use of the
-   quarantine feature.
-
- * Broken &&-chains in the test scripts have been corrected.
-
- * The RCS keyword substitution in "git p4" used to be done assuming
-   that the contents are UTF-8 text, which can trigger decoding
-   errors.  We now treat the contents as a bytestring for robustness
-   and correctness.
-
- * The conditions to choose different definitions of the FLEX_ARRAY
-   macro for vendor compilers has been simplified to make it easier to
-   maintain.
-
- * Correctness and performance update to "diff --color-moved" feature.
-
- * "git upload-pack" (the other side of "git fetch") used a 8kB buffer
-   but most of its payload came on 64kB "packets".  The buffer size
-   has been enlarged so that such a packet fits.
-
- * "git fetch" and "git pull" are now declared sparse-index clean.
-   Also "git ls-files" learns the "--sparse" option to help debugging.
-
- * Similar message templates have been consolidated so that
-   translators need to work on fewer number of messages.
-
-
-Fixes since v2.34
------------------
-
- * "git grep" looking in a blob that has non-UTF8 payload was
-   completely broken when linked with certain versions of PCREv2
-   library in the latest release.
-
- * Other code cleanup, docfix, build fix, etc.
-
- * "git pull" with any strategy when the other side is behind us
-   should succeed as it is a no-op, but doesn't.
-
- * An earlier change in 2.34.0 caused JGit application (that abused
-   GIT_EDITOR mechanism when invoking "git config") to get stuck with
-   a SIGTTOU signal; it has been reverted.
-
- * An earlier change that broke .gitignore matching has been reverted.
-
- * Things like "git -c branch.sort=bogus branch new HEAD", i.e. the
-   operation modes of the "git branch" command that do not need the
-   sort key information, no longer errors out by seeing a bogus sort
-   key.
-   (merge 98e7ab6d42 jc/fix-ref-sorting-parse later to maint).
-
- * The compatibility implementation for unsetenv(3) were written to
-   mimic ancient, non-POSIX, variant seen in an old glibc; it has been
-   changed to return an integer to match the more modern era.
-   (merge a38989bd5b jc/unsetenv-returns-an-int later to maint).
-
- * The clean/smudge conversion code path has been prepared to better
-   work on platforms where ulong is narrower than size_t.
-   (merge 596b5e77c9 mc/clean-smudge-with-llp64 later to maint).
-
- * Redact the path part of packfile URI that appears in the trace output.
-   (merge 0ba558ffb1 if/redact-packfile-uri later to maint).
-
- * CI has been taught to catch some Unicode directional formatting
-   sequence that can be used in certain mischief.
-   (merge 0e7696c64d js/ci-no-directional-formatting later to maint).
-
- * The "--date=format:<strftime>" gained a workaround for the lack of
-   system support for a non-local timezone to handle "%s" placeholder.
-   (merge 9b591b9403 jk/strbuf-addftime-seconds-since-epoch later to maint).
-
- * The "merge" subcommand of "git jump" (in contrib/) silently ignored
-   pathspec and other parameters.
-   (merge 67ba13e5a4 jk/jump-merge-with-pathspec later to maint).
-
- * The code to decode the length of packed object size has been
-   corrected.
-   (merge 34de5b8eac jt/pack-header-lshift-overflow later to maint).
-
- * The advice message given by "git pull" when the user hasn't made a
-   choice between merge and rebase still said that the merge is the
-   default, which no longer is the case.  This has been corrected.
-   (merge 71076d0edd ah/advice-pull-has-no-preference-between-rebase-and-merge later to maint).
-
- * "git fetch", when received a bad packfile, can fail with SIGPIPE.
-   This wasn't wrong per-se, but we now detect the situation and fail
-   in a more predictable way.
-   (merge 2a4aed42ec jk/fetch-pack-avoid-sigpipe-to-index-pack later to maint).
-
- * The function to cull a child process and determine the exit status
-   had two separate code paths for normal callers and callers in a
-   signal handler, and the latter did not yield correct value when the
-   child has caught a signal.  The handling of the exit status has
-   been unified for these two code paths.  An existing test with
-   flakiness has also been corrected.
-   (merge 5263e22cba jk/t7006-sigpipe-tests-fix later to maint).
-
- * When a non-existent program is given as the pager, we tried to
-   reuse an uninitialized child_process structure and crashed, which
-   has been fixed.
-   (merge f917f57f40 em/missing-pager later to maint).
-
- * The single-key-input mode in "git add -p" had some code to handle
-   keys that generate a sequence of input via ReadKey(), which did not
-   handle end-of-file correctly, which has been fixed.
-   (merge fc8a8126df cb/add-p-single-key-fix later to maint).
-
- * "git rebase -x" added an unnecessary 'exec' instructions before
-   'noop', which has been corrected.
-   (merge cc9dcdee61 en/rebase-x-fix later to maint).
-
- * When the "git push" command is killed while the receiving end is
-   trying to report what happened to the ref update proposals, the
-   latter used to die, due to SIGPIPE.  The code now ignores SIGPIPE
-   to increase our chances to run the post-receive hook after it
-   happens.
-   (merge d34182b9e3 rj/receive-pack-avoid-sigpipe-during-status-reporting later to maint).
-
- * "git worktree add" showed "Preparing worktree" message to the
-   standard output stream, but when it failed, the message from die()
-   went to the standard error stream.  Depending on the order the
-   stdio streams are flushed at the program end, this resulted in
-   confusing output.  It has been corrected by sending all the chatty
-   messages to the standard error stream.
-   (merge b50252484f es/worktree-chatty-to-stderr later to maint).
-
- * Coding guideline document has been updated to clarify what goes to
-   standard error in our system.
-   (merge e258eb4800 es/doc-stdout-vs-stderr later to maint).
-
- * The sparse-index/sparse-checkout feature had a bug in its use of
-   the matching code to determine which path is in or outside the
-   sparse checkout patterns.
-   (merge 8c5de0d265 ds/sparse-deep-pattern-checkout-fix later to maint).
-
- * "git rebase -x" by mistake started exporting the GIT_DIR and
-   GIT_WORK_TREE environment variables when the command was rewritten
-   in C, which has been corrected.
-   (merge 434e0636db en/rebase-x-wo-git-dir-env later to maint).
-
- * When "git log" implicitly enabled the "decoration" processing
-   without being explicitly asked with "--decorate" option, it failed
-   to read and honor the settings given by the "--decorate-refs"
-   option.
-
- * "git fetch --set-upstream" did not check if there is a current
-   branch, leading to a segfault when it is run on a detached HEAD,
-   which has been corrected.
-   (merge 17baeaf82d ab/fetch-set-upstream-while-detached later to maint).
-
- * Among some code paths that ask an yes/no question, only one place
-   gave a prompt that looked different from the others, which has been
-   updated to match what the others create.
-   (merge 0fc8ed154c km/help-prompt-fix later to maint).
-
- * "git log --invert-grep --author=<name>" used to exclude commits
-   written by the given author, but now "--invert-grep" only affects
-   the matches made by the "--grep=<pattern>" option.
-   (merge 794c000267 rs/log-invert-grep-with-headers later to maint).
-
- * "git grep --perl-regexp" failed to match UTF-8 characters with
-   wildcard when the pattern consists only of ASCII letters, which has
-   been corrected.
-   (merge 32e3e8bc55 rs/pcre2-utf later to maint).
-
- * Certain sparse-checkout patterns that are valid in non-cone mode
-   led to segfault in cone mode, which has been corrected.
-
- * Use of certain "git rev-list" options with "git fast-export"
-   created nonsense results (the worst two of which being "--reverse"
-   and "--invert-grep --grep=<foo>").  The use of "--first-parent" is
-   made to behave a bit more sensible than before.
-   (merge 726a228dfb ws/fast-export-with-revision-options later to maint).
-
- * Perf tests were run with end-user's shell, but it has been
-   corrected to use the shell specified by $TEST_SHELL_PATH.
-   (merge 9ccab75608 ja/perf-use-specified-shell later to maint).
-
- * Fix dependency rules to generate hook-list.h header file.
-   (merge d3fd1a6667 ab/makefile-hook-list-dependency-fix later to maint).
-
- * "git stash" by default triggers its "push" action, but its
-   implementation also made "git stash -h" to show short help only for
-   "git stash push", which has been corrected.
-   (merge ca7990cea5 ab/do-not-limit-stash-help-to-push later to maint).
-
- * "git apply --3way" bypasses the attempt to do a three-way
-   application in more cases to address the regression caused by the
-   recent change to use direct application as a fallback.
-   (merge 34d607032c jz/apply-3-corner-cases later to maint).
-
- * Fix performance-releated bug in "git subtree" (in contrib/).
-   (merge 3ce8888fb4 jl/subtree-check-parents-argument-passing-fix later to maint).
-
- * Extend the guidance to choose the base commit to build your work
-   on, and hint/nudge contributors to read others' changes.
-   (merge fdfae830f8 jc/doc-submitting-patches-choice-of-base later to maint).
-
- * A corner case bug in the ort merge strategy has been corrected.
-   (merge d30126c20d en/merge-ort-renorm-with-rename-delete-conflict-fix later to maint).
-
- * "git stash apply" forgot to attempt restoring untracked files when
-   it failed to restore changes to tracked ones.
-   (merge 71cade5a0b en/stash-df-fix later to maint).
-
- * Calling dynamically loaded functions on Windows has been corrected.
-   (merge 4a9b204920 ma/windows-dynload-fix later to maint).
-
- * Some lockfile code called free() in signal-death code path, which
-   has been corrected.
-   (merge 58d4d7f1c5 ps/lockfile-cleanup-fix later to maint).
-
- * Other code cleanup, docfix, build fix, etc.
-   (merge 74db416c9c cw/protocol-v2-doc-fix later to maint).
-   (merge f9b2b6684d ja/doc-cleanup later to maint).
-   (merge 7d1b866778 jc/fix-first-object-walk later to maint).
-   (merge 538ac74604 js/trace2-avoid-recursive-errors later to maint).
-   (merge 152923b132 jk/t5319-midx-corruption-test-deflake later to maint).
-   (merge 9081a421a6 ab/checkout-branch-info-leakfix later to maint).
-   (merge 42c456ff81 rs/mergesort later to maint).
-   (merge ad506e6780 tl/midx-docfix later to maint).
-   (merge bf5b83fd8a hk/ci-checkwhitespace-commentfix later to maint).
-   (merge 49f1eb3b34 jk/refs-g11-workaround later to maint).
-   (merge 7d3fc7df70 jt/midx-doc-fix later to maint).
-   (merge 7b089120d9 hn/create-reflog-simplify later to maint).
-   (merge 9e12400da8 cb/mingw-gmtime-r later to maint).
-   (merge 0bf0de6cc7 tb/pack-revindex-on-disk-cleanup later to maint).
-   (merge 2c68f577fc ew/cbtree-remove-unused-and-broken-cb-unlink later to maint).
-   (merge eafd6e7e55 ab/die-with-bug later to maint).
-   (merge 91028f7659 jc/grep-patterntype-default-doc later to maint).
-   (merge 47ca93d071 ds/repack-fixlets later to maint).
-   (merge e6a9bc0c60 rs/t4202-invert-grep-test-fix later to maint).
-   (merge deb5407a42 gh/gpg-doc-markup-fix later to maint).
-   (merge 999bba3e0b rs/daemon-plug-leak later to maint).
-   (merge 786eb1ba39 js/l10n-mention-ngettext-early-in-readme later to maint).
-   (merge 2f12b31b74 ab/makefile-msgfmt-wo-stats later to maint).
-   (merge 0517f591ca fs/gpg-unknown-key-test-fix later to maint).
-   (merge 97d6fb5a1f ma/header-dup-cleanup later to maint).

Documentation/RelNotes/2.35.1.txt

@@ -1,6 +0,0 @@
-Git v2.35.1 Release Notes
-=========================
-
-Git 2.35 shipped with a regression that broke use of "rebase" and
-"stash" in a secondary worktree.  This maintenance release ought to
-fix it.

Documentation/RelNotes/2.35.2.txt

@@ -1,7 +0,0 @@
-Git v2.35.2 Release Notes
-=========================
-
-This release merges up the fixes that appear in v2.30.3,
-v2.31.2, v2.32.1, v2.33.2 and v2.34.2 to address the security
-issue CVE-2022-24765; see the release notes for these versions
-for details.

Documentation/RelNotes/2.35.3.txt

@@ -1,4 +0,0 @@
-Git Documentation/RelNotes/2.35.3.txt Release Notes
-=========================
-
-This release merges up the fixes that appear in v2.35.3.

Documentation/RelNotes/2.36.0.txt

@@ -1,429 +0,0 @@
-Git 2.36 Release Notes
-======================
-
-Updates since Git 2.35
-----------------------
-
-Backward compatibility warts
-
- * "git name-rev --stdin" has been deprecated and issues a warning
-   when used; use "git name-rev --annotate-stdin" instead.
-
- * "git clone --filter=... --recurse-submodules" only makes the
-   top-level a partial clone, while submodules are fully cloned.  This
-   behaviour is changed to pass the same filter down to the submodules.
-
- * With the fixes for CVE-2022-24765 that are common with versions of
-   Git 2.30.4, 2.31.3, 2.32.2, 2.33.3, 2.34.3, and 2.35.3, Git has
-   been taught not to recognise repositories owned by other users, in
-   order to avoid getting affected by their config files and hooks.
-   You can list the path to the safe/trusted repositories that may be
-   owned by others on a multi-valued configuration variable
-   `safe.directory` to override this behaviour, or use '*' to declare
-   that you trust anything.
-
-
-Note to those who build from the source
-
- * Since Git 2.31, our source assumed that the compiler you use to
-   build Git supports variadic macros, with an easy-to-use escape
-   hatch to allow compilation without variadic macros with an request
-   to report that you had to use the escape hatch to the list.
-   Because we haven't heard from anybody who actually needed to use
-   the escape hatch, it has been removed, making support of variadic
-   macros a hard requirement.
-
-
-UI, Workflows & Features
-
- * Assorted updates to "git cat-file", especially "-h".
-
- * The command line completion (in contrib/) learns to complete
-   arguments to give to "git sparse-checkout" command.
-
- * "git log --remerge-diff" shows the difference from mechanical merge
-   result and the result that is actually recorded in a merge commit.
-
- * "git log" and friends learned an option --exclude-first-parent-only
-   to propagate UNINTERESTING bit down only along the first-parent
-   chain, just like --first-parent option shows commits that lack the
-   UNINTERESTING bit only along the first-parent chain.
-
- * The command line completion script (in contrib/) learned to
-   complete all Git subcommands, including the ones that are normally
-   hidden, when GIT_COMPLETION_SHOW_ALL_COMMANDS is used.
-
- * "git branch" learned the "--recurse-submodules" option.
-
- * A user can forget to make a script file executable before giving
-   it to "git bisect run".  In such a case, all tests will exit with
-   126 or 127 error codes, even on revisions that are marked as good.
-   Try to recognize this situation and stop iteration early.
-
- * When "index-pack" dies due to incoming data exceeding the maximum
-   allowed input size, include the value of the limit in the error
-   message.
-
- * The error message given by "git switch HEAD~4" has been clarified
-   to suggest the "--detach" option that is required.
-
- * In sparse-checkouts, files mis-marked as missing from the working tree
-   could lead to later problems.  Such files were hard to discover, and
-   harder to correct.  Automatically detecting and correcting the marking
-   of such files has been added to avoid these problems.
-
- * "git cat-file" learns "--batch-command" mode, which is a more
-   flexible interface than the existing "--batch" or "--batch-check"
-   modes, to allow different kinds of inquiries made.
-
- * The level of verbose output from the ort backend during inner merge
-   has been aligned to that of the recursive backend.
-
- * "git remote rename A B", depending on the number of remote-tracking
-   refs involved, takes long time renaming them.  The command has been
-   taught to show progress bar while making the user wait.
-
- * Bundle file format gets extended to allow a partial bundle,
-   filtered by similar criteria you would give when making a
-   partial/lazy clone.
-
- * A new built-in userdiff driver for kotlin has been added.
-
- * "git repack" learned a new configuration to disable triggering of
-   age-old "update-server-info" command, which is rarely useful these
-   days.
-
- * "git stash" does not allow subcommands it internally runs as its
-   implementation detail, except for "git reset", to emit messages;
-   now "git reset" part has also been squelched.
-
- * "git ls-tree" learns "--oid-only" option, similar to "--name-only",
-   and more generalized "--format" option.
-
- * "git fetch --refetch" learned to fetch everything without telling
-   the other side what we already have, which is useful when you
-   cannot trust what you have in the local object store.
-
- * "git branch" gives hint when branch tracking cannot be established
-   because fetch refspecs from multiple remote repositories overlap.
-
- * "git worktree list --porcelain" did not c-quote pathnames and lock
-   reasons with unsafe bytes correctly, which is worked around by
-   introducing NUL terminated output format with "-z".
-
-
-Performance, Internal Implementation, Development Support etc.
-
- * "git apply" (ab)used the util pointer of the string-list to keep
-   track of how each symbolic link needs to be handled, which has been
-   simplified by using strset.
-
- * Fix a hand-rolled alloca() imitation that may have violated
-   alignment requirement of data being sorted in compatibility
-   implementation of qsort_s() and stable qsort().
-
- * Use the parse-options API in "git reflog" command.
-
- * The conditional inclusion mechanism of configuration files using
-   "[includeIf <condition>]" learns to base its decision on the
-   URL of the remote repository the repository interacts with.
-   (merge 399b198489 jt/conditional-config-on-remote-url later to maint).
-
- * "git name-rev --stdin" does not behave like usual "--stdin" at
-   all.  Start the process of renaming it to "--annotate-stdin".
-   (merge a2585719b3 jc/name-rev-stdin later to maint).
-
- * "git update-index", "git checkout-index", and "git clean" are
-   taught to work better with the sparse checkout feature.
-
- * Use an internal call to reset_head() helper function instead of
-   spawning "git checkout" in "rebase", and update code paths that are
-   involved in the change.
-
- * Messages "ort" merge backend prepares while dealing with conflicted
-   paths were unnecessarily confusing since it did not differentiate
-   inner merges and outer merges.
-
- * Small modernization of the rerere-train script (in contrib/).
-
- * Use designated initializers we started using in mid 2017 in more
-   parts of the codebase that are relatively quiescent.
-
- * Improve failure case behaviour of xdiff library when memory
-   allocation fails.
-
- * General clean-up in reftable implementation, including
-   clarification of the API documentation, tightening the code to
-   honor documented length limit, etc.
-
- * Remove the escape hatch we added when we introduced the weather
-   balloon to use variadic macros unconditionally, to make it official
-   that we now have a hard dependency on the feature.
-
- * Makefile refactoring with a bit of suffixes rule stripping to
-   optimize the runtime overhead.
-
- * "git stash drop" is reimplemented as an internal call to
-   reflog_delete() function, instead of invoking "git reflog delete"
-   via run_command() API.
-
- * Count string_list items in size_t, not "unsigned int".
-
- * The single-key interactive operation used by "git add -p" has been
-   made more robust.
-
- * Remove unneeded <meta http-equiv=content-type...> from gitweb
-   output.
-
- * "git name-rev" learned to use the generation numbers when setting
-   the lower bound of searching commits used to explain the revision,
-   when available, instead of committer time.
-
- * Replace core.fsyncObjectFiles with two new configuration variables,
-   core.fsync and core.fsyncMethod.
-
- * Updates to refs traditionally weren't fsync'ed, but we can
-   configure using core.fsync variable to do so.
-
- * "git reflog" command now uses parse-options API to parse its
-   command line options.
-
-
-Fixes since v2.35
------------------
-
- * "rebase" and "stash" in secondary worktrees are broken in
-   Git 2.35.0, which has been corrected.
-
- * "git pull --rebase" ignored the rebase.autostash configuration
-   variable when the remote history is a descendant of our history,
-   which has been corrected.
-   (merge 3013d98d7a pb/pull-rebase-autostash-fix later to maint).
-
- * "git update-index --refresh" has been taught to deal better with
-   racy timestamps (just like "git status" already does).
-   (merge 2ede073fd2 ms/update-index-racy later to maint).
-
- * Avoid tests that are run under GIT_TRACE2 set from failing
-   unnecessarily.
-   (merge 944d808e42 js/test-unset-trace2-parents later to maint).
-
- * The merge-ort misbehaved when merge.renameLimit configuration is
-   set too low and failed to find all renames.
-   (merge 9ae39fef7f en/merge-ort-restart-optim-fix later to maint).
-
- * We explain that revs come first before the pathspec among command
-   line arguments, but did not spell out that dashed options come
-   before other args, which has been corrected.
-   (merge c11f95010c tl/doc-cli-options-first later to maint).
-
- * "git add -p" rewritten in C regressed hunk splitting in some cases,
-   which has been corrected.
-   (merge 7008ddc645 pw/add-p-hunk-split-fix later to maint).
-
- * "git fetch --negotiate-only" is an internal command used by "git
-   push" to figure out which part of our history is missing from the
-   other side.  It should never recurse into submodules even when
-   fetch.recursesubmodules configuration variable is set, nor it
-   should trigger "gc".  The code has been tightened up to ensure it
-   only does common ancestry discovery and nothing else.
-   (merge de4eaae63a gc/fetch-negotiate-only-early-return later to maint).
-
- * The code path that verifies signatures made with ssh were made to
-   work better on a system with CRLF line endings.
-   (merge caeef01ea7 fs/ssh-signing-crlf later to maint).
-
- * "git sparse-checkout init" failed to write into $GIT_DIR/info
-   directory when the repository was created without one, which has
-   been corrected to auto-create it.
-   (merge 7f44842ac1 jt/sparse-checkout-leading-dir-fix later to maint).
-
- * Cloning from a repository that does not yet have any branches or
-   tags but has other refs resulted in a "remote transport reported
-   error", which has been corrected.
-   (merge dccea605b6 jt/clone-not-quite-empty later to maint).
-
- * Mark in various places in the code that the sparse index and the
-   split index features are mutually incompatible.
-   (merge 451b66c533 js/sparse-vs-split-index later to maint).
-
- * Update the logic to compute alignment requirement for our mem-pool.
-   (merge e38bcc66d8 jc/mem-pool-alignment later to maint).
-
- * Pick a better random number generator and use it when we prepare
-   temporary filenames.
-   (merge 47efda967c bc/csprng-mktemps later to maint).
-
- * Update the contributor-facing documents on proposed log messages.
-   (merge cdba0295b0 jc/doc-log-messages later to maint).
-
- * When "git fetch --prune" failed to prune the refs it wanted to
-   prune, the command issued error messages but exited with exit
-   status 0, which has been corrected.
-   (merge c9e04d905e tg/fetch-prune-exit-code-fix later to maint).
-
- * Problems identified by Coverity in the reftable code have been
-   corrected.
-   (merge 01033de49f hn/reftable-coverity-fixes later to maint).
-
- * A bug that made multi-pack bitmap and the object order out-of-sync,
-   making the .midx data corrupt, has been fixed.
-   (merge f8b60cf99b tb/midx-bitmap-corruption-fix later to maint).
-
- * The build procedure has been taught to notice older version of zlib
-   and enable our replacement uncompress2() automatically.
-   (merge 07564773c2 ab/auto-detect-zlib-compress2 later to maint).
-
- * Interaction between fetch.negotiationAlgorithm and
-   feature.experimental configuration variables has been corrected.
-   (merge 714edc620c en/fetch-negotiation-default-fix later to maint).
-
- * "git diff --diff-filter=aR" is now parsed correctly.
-   (merge 75408ca949 js/diff-filter-negation-fix later to maint).
-
- * When "git subtree" wants to create a merge, it used "git merge" and
-   let it be affected by end-user's "merge.ff" configuration, which
-   has been corrected.
-   (merge 9158a3564a tk/subtree-merge-not-ff-only later to maint).
-
- * Unlike "git apply", "git patch-id" did not handle patches with
-   hunks that has only 1 line in either preimage or postimage, which
-   has been corrected.
-   (merge 757e75c81e jz/patch-id-hunk-header-parsing-fix later to maint).
-
- * "receive-pack" checks if it will do any ref updates (various
-   conditions could reject a push) before received objects are taken
-   out of the temporary directory used for quarantine purposes, so
-   that a push that is known-to-fail will not leave crufts that a
-   future "gc" needs to clean up.
-   (merge 5407764069 cb/clear-quarantine-early-on-all-ref-update-errors later to maint).
-
- * When there is no object to write .bitmap file for, "git
-   multi-pack-index" triggered an error, instead of just skipping,
-   which has been corrected.
-   (merge eb57277ba3 tb/midx-no-bitmap-for-no-objects later to maint).
-
- * "git cmd -h" outside a repository should error out cleanly for many
-   commands, but instead it hit a BUG(), which has been corrected.
-   (merge 87ad07d735 js/short-help-outside-repo-fix later to maint).
-
- * "working tree" and "per-worktree ref" were in glossary, but
-   "worktree" itself wasn't, which has been corrected.
-   (merge 2df5387ed0 jc/glossary-worktree later to maint).
-
- * L10n support for a few error messages.
-   (merge 3d3c23b3a7 bs/forbid-i18n-of-protocol-token-in-fetch-pack later to maint).
-
- * Test modernization.
-   (merge d4fe066e4b sy/t0001-use-path-is-helper later to maint).
-
- * "git log --graph --graph" used to leak a graph structure, and there
-   was no way to countermand "--graph" that appear earlier on the
-   command line.  A "--no-graph" option has been added and resource
-   leakage has been plugged.
-
- * Error output given in response to an ambiguous object name has been
-   improved.
-   (merge 3a73c1dfaf ab/ambiguous-object-name later to maint).
-
- * "git sparse-checkout" wants to work with per-worktree configuration,
-   but did not work well in a worktree attached to a bare repository.
-   (merge 3ce1138272 ds/sparse-checkout-requires-per-worktree-config later to maint).
-
- * Setting core.untrackedCache to true failed to add the untracked
-   cache extension to the index.
-
- * Workaround we have for versions of PCRE2 before their version 10.36
-   were in effect only for their versions newer than 10.36 by mistake,
-   which has been corrected.
-   (merge 97169fc361 rs/pcre-invalid-utf8-fix-fix later to maint).
-
- * Document Taylor as a new member of Git PLC at SFC.  Welcome.
-   (merge e8d56ca863 tb/coc-plc-update later to maint).
-
- * "git checkout -b branch/with/multi/level/name && git stash" only
-   recorded the last level component of the branch name, which has
-   been corrected.
-
- * Check the return value from parse_tree_indirect() to turn segfaults
-   into calls to die().
-   (merge 8d2eaf649a gc/parse-tree-indirect-errors later to maint).
-
- * Newer version of GPGSM changed its output in a backward
-   incompatible way to break our code that parses its output.  It also
-   added more processes our tests need to kill when cleaning up.
-   Adjustments have been made to accommodate these changes.
-   (merge b0b70d54c4 fs/gpgsm-update later to maint).
-
- * The untracked cache newly computed weren't written back to the
-   on-disk index file when there is no other change to the index,
-   which has been corrected.
-
- * "git config -h" did not describe the "--type" option correctly.
-   (merge 5445124fad mf/fix-type-in-config-h later to maint).
-
- * The way generation number v2 in the commit-graph files are
-   (not) handled has been corrected.
-   (merge 6dbf4b8172 ds/commit-graph-gen-v2-fixes later to maint).
-
- * The method to trigger malloc check used in our tests no longer work
-   with newer versions of glibc.
-   (merge baedc59543 ep/test-malloc-check-with-glibc-2.34 later to maint).
-
- * When "git fetch --recurse-submodules" grabbed submodule commits
-   that would be needed to recursively check out newly fetched commits
-   in the superproject, it only paid attention to submodules that are
-   in the current checkout of the superproject.  We now do so for all
-   submodules that have been run "git submodule init" on.
-
- * "git rebase $base $non_branch_commit", when $base is an ancestor or
-   the $non_branch_commit, modified the current branch, which has been
-   corrected.
-
- * When "shallow" information is updated, we forgot to update the
-   in-core equivalent, which has been corrected.
-
- * When creating a loose object file, we didn't report the exact
-   filename of the file we failed to fsync, even though the
-   information was readily available, which has been corrected.
-
- * "git am" can read from the standard input when no mailbox is given
-   on the command line, but the end-user gets no indication when it
-   happens, making Git appear stuck.
-   (merge 7b20af6a06 jc/mailsplit-warn-on-tty later to maint).
-
- * "git mv" failed to refresh the cached stat information for the
-   entry it moved.
-   (merge b7f9130a06 vd/mv-refresh-stat later to maint).
-
- * Other code cleanup, docfix, build fix, etc.
-   (merge cfc5cf428b jc/find-header later to maint).
-   (merge 40e7cfdd46 jh/p4-fix-use-of-process-error-exception later to maint).
-   (merge 727e6ea350 jh/p4-spawning-external-commands-cleanup later to maint).
-   (merge 0a6adc26e2 rs/grep-expr-cleanup later to maint).
-   (merge 4ed7dfa713 po/readme-mention-contributor-hints later to maint).
-   (merge 6046f7a91c en/plug-leaks-in-merge later to maint).
-   (merge 8c591dbfce bc/clarify-eol-attr later to maint).
-   (merge 518e15db74 rs/parse-options-lithelp-help later to maint).
-   (merge cbac0076ef gh/doc-typos later to maint).
-   (merge ce14de03db ab/no-errno-from-resolve-ref-unsafe later to maint).
-   (merge 2826ffad8c rc/negotiate-only-typofix later to maint).
-   (merge 0f03f04c5c en/sparse-checkout-leakfix later to maint).
-   (merge 74f3390dde sy/diff-usage-typofix later to maint).
-   (merge 45d0212a71 ll/doc-mktree-typofix later to maint).
-   (merge e9b272e4c1 js/no-more-legacy-stash later to maint).
-   (merge 6798b08e84 ab/do-not-hide-failures-in-git-dot-pm later to maint).
-   (merge 9325285df4 po/doc-check-ignore-markup-fix later to maint).
-   (merge cd26cd6c7c sy/modernize-t-lib-read-tree-m-3way later to maint).
-   (merge d17294a05e ab/hash-object-leakfix later to maint).
-   (merge b8403129d3 jd/t0015-modernize later to maint).
-   (merge 332acc248d ds/mailmap later to maint).
-   (merge 04bf052eef ab/grep-patterntype later to maint).
-   (merge 6ee36364eb ab/diff-free-more later to maint).
-   (merge 63a36017fe nj/read-tree-doc-reffix later to maint).
-   (merge eed36fce38 sm/no-git-in-upstream-of-pipe-in-tests later to maint).
-   (merge c614beb933 ep/t6423-modernize later to maint).
-   (merge 57be9c6dee ab/reflog-prep-fix later to maint).
-   (merge 5327d8982a js/in-place-reverse-in-sequencer later to maint).
-   (merge 2e2c0be51e dp/worktree-repair-in-usage later to maint).
-   (merge 6563706568 jc/coding-guidelines-decl-in-for-loop later to maint).

Documentation/RelNotes/2.36.1.txt

@@ -1,33 +0,0 @@
-Git v2.36.1 Release Notes
-=========================
-
-Fixes since v2.36
------------------
-
- * "git submodule update" without pathspec should silently skip an
-   uninitialized submodule, but it started to become noisy by mistake.
-
- * "diff-tree --stdin" has been broken for about a year, but 2.36
-   release broke it even worse by breaking running the command with
-   <pathspec>, which in turn broke "gitk" and got noticed.  This has
-   been corrected by aligning its behaviour to that of "log".
-
- * Regression fix for 2.36 where "git name-rev" started to sometimes
-   reference strings after they are freed.
-
- * "git show <commit1> <commit2>... -- <pathspec>" lost the pathspec
-   when showing the second and subsequent commits, which has been
-   corrected.
-
- * "git fast-export -- <pathspec>" lost the pathspec when showing the
-   second and subsequent commits, which has been corrected.
-
- * "git format-patch <args> -- <pathspec>" lost the pathspec when
-   showing the second and subsequent commits, which has been
-   corrected.
-
- * Get rid of a bogus and over-eager coccinelle rule.
-
- * Correct choices of C compilers used in various CI jobs.
-
-Also contains minor documentation updates and code clean-ups.

Documentation/RelNotes/2.36.2.txt

@@ -1,50 +0,0 @@
-Git v2.36.2 Release Notes
-=========================
-
-This maintenance release is primarily to merge down updates to the
-build and CI procedures from the 'master' front, in order to ensure
-that we can cut healthy maintenance releases in the future.  It also
-contains a handful of small and trivially-correct bugfixes.
-
-Fixes since v2.36.1
--------------------
-
- * Fixes real problems noticed by gcc 12 and works around false
-   positives.
-
- * Update URL to the gitk repository.
-
- * The "--current" option of "git show-branch" should have been made
-   incompatible with the "--reflog" mode, but this was not enforced,
-   which has been corrected.
-
- * "git archive --add-file=<path>" picked up the raw permission bits
-   from the path and propagated to zip output in some cases, without
-   normalization, which has been corrected (tar output did not have
-   this issue).
-
- * A bit of test framework fixes with a few fixes to issues found by
-   valgrind.
-
- * macOS CI jobs have been occasionally flaky due to tentative version
-   skew between perforce and the homebrew packager.  Instead of
-   failing the whole CI job, just let it skip the p4 tests when this
-   happens.
-
- * The commit summary shown after making a commit is matched to what
-   is given in "git status" not to use the break-rewrite heuristics.
-
- * Avoid problems from interaction between malloc_check and address
-   sanitizer.
-
- * "git rebase --keep-base <upstream> <branch-to-rebase>" computed the
-   commit to rebase onto incorrectly, which has been corrected.
-
- * The path taken by "git multi-pack-index" command from the end user
-   was compared with path internally prepared by the tool withut first
-   normalizing, which lead to duplicated paths not being noticed,
-   which has been corrected.
-
- * "git clone --origin X" leaked piece of memory that held value read
-   from the clone.defaultRemoteName configuration variable, which has
-   been plugged.

Documentation/RelNotes/2.37.0.txt

@@ -1,337 +0,0 @@
-Git v2.37 Release Notes
-=======================
-
-UI, Workflows & Features
-
- * "vimdiff[123]" mergetool drivers have been reimplemented with a
-   more generic layout mechanism.
-
- * "git -v" and "git -h" are now understood as "git --version" and
-   "git --help".
-
- * The temporary files fed to external diff command are now generated
-   inside a new temporary directory under the same basename.
-
- * "git log --since=X" will stop traversal upon seeing a commit that
-   is older than X, but there may be commits behind it that is younger
-   than X when the commit was created with a faulty clock.  A new
-   option is added to keep digging without stopping, and instead
-   filter out commits with timestamp older than X.
-
- * "git -c branch.autosetupmerge=simple branch $A $B" will set the $B
-   as $A's upstream only when $A and $B shares the same name, and "git
-   -c push.default=simple" on branch $A would push to update the
-   branch $A at the remote $B came from.  Also more places use the
-   sole remote, if exists, before defaulting to 'origin'.
-
- * A new doc has been added that lists tips for tools to work with
-   Git's codebase.
-
- * "git remote -v" now shows the list-objects-filter used during
-   fetching from the remote, if available.
-
- * With the new http.curloptResolve configuration, the CURLOPT_RESOLVE
-   mechanism that allows cURL based applications to use pre-resolved
-   IP addresses for the requests is exposed to the scripts.
-
- * "git add -i" was rewritten in C some time ago and has been in
-   testing; the reimplementation is now exposed to general public by
-   default.
-
- * Deprecate non-cone mode of the sparse-checkout feature.
-
- * Introduce a filesystem-dependent mechanism to optimize the way the
-   bits for many loose object files are ensured to hit the disk
-   platter.
-
- * The "do not remove the directory the user started Git in" logic,
-   when Git cannot tell where that directory is, is disabled.  Earlier
-   we refused to run in such a case.
-
- * A mechanism to pack unreachable objects into a "cruft pack",
-   instead of ejecting them into loose form to be reclaimed later, has
-   been introduced.
-
- * Update the doctype written in gitweb output to xhtml5.
-
- * The "transfer.credentialsInURL" configuration variable controls what
-   happens when a URL with embedded login credential is used on either
-   "fetch" or "push". Credentials are currently only detected in
-   `remote.<name>.url` config, not `remote.<name>.pushurl`.
-
- * "git revert" learns "--reference" option to use more human-readable
-   reference to the commit it reverts in the message template it
-   prepares for the user.
-
- * Various error messages that talk about the removal of
-   "--preserve-merges" in "rebase" have been strengthened, and "rebase
-   --abort" learned to get out of a state that was left by an earlier
-   use of the option.
-
-
-Performance, Internal Implementation, Development Support etc.
-
- * The performance of the "untracked cache" feature has been improved
-   when "--untracked-files=<mode>" and "status.showUntrackedFiles"
-   are combined.
-
- * "git stash" works better with sparse index entries.
-
- * "git show :<path>" learned to work better with the sparse-index
-   feature.
-
- * Introduce and apply coccinelle rule to discourage an explicit
-   comparison between a pointer and NULL, and applies the clean-up to
-   the maintenance track.
-
- * Preliminary code refactoring around transport and bundle code.
-
- * "sparse-checkout" learns to work better with the sparse-index
-   feature.
-
- * A workflow change for translators are being proposed.  git.pot is
-   no longer version controlled and it is local responsibility of
-   translators to generate it.
-
- * Plug the memory leaks from the trickiest API of all, the revision
-   walker.
-
- * Rename .env_array member to .env in the child_process structure.
-
-  * The fsmonitor--daemon handles even more corner cases when
-    watching filesystem events.
-
- * A new bug() and BUG_if_bug() API is introduced to make it easier to
-   uniformly log "detect multiple bugs and abort in the end" pattern.
-
-
-Fixes since v2.36
------------------
-
- * "git submodule update" without pathspec should silently skip an
-   uninitialized submodule, but it started to become noisy by mistake.
-   (merge 4f1ccef87c gc/submodule-update-part2 later to maint).
-
- * "diff-tree --stdin" has been broken for about a year, but 2.36
-   release broke it even worse by breaking running the command with
-   <pathspec>, which in turn broke "gitk" and got noticed.  This has
-   been corrected by aligning its behaviour to that of "log".
-   (merge f8781bfda3 jc/diff-tree-stdin-fix later to maint).
-
- * Regression fix for 2.36 where "git name-rev" started to sometimes
-   reference strings after they are freed.
-   (merge 45a14f578e rs/name-rev-fix-free-after-use later to maint).
-
- * "git show <commit1> <commit2>... -- <pathspec>" lost the pathspec
-   when showing the second and subsequent commits, which has been
-   corrected.
-   (merge 5cdb38458e jc/show-pathspec-fix later to maint).
-
- * "git fast-export -- <pathspec>" lost the pathspec when showing the
-   second and subsequent commits, which has been corrected.
-   (merge d1c25272f5 rs/fast-export-pathspec-fix later to maint).
-
- * "git format-patch <args> -- <pathspec>" lost the pathspec when
-   showing the second and subsequent commits, which has been
-   corrected.
-   (merge 91f8f7e46f rs/format-patch-pathspec-fix later to maint).
-
- * "git clone --origin X" leaked piece of memory that held value read
-   from the clone.defaultRemoteName configuration variable, which has
-   been plugged.
-   (merge 6dfadc8981 jc/clone-remote-name-leak-fix later to maint).
-
- * Get rid of a bogus and over-eager coccinelle rule.
-   (merge 08bdd3a185 jc/cocci-xstrdup-or-null-fix later to maint).
-
- * The path taken by "git multi-pack-index" command from the end user
-   was compared with path internally prepared by the tool without first
-   normalizing, which lead to duplicated paths not being noticed,
-   which has been corrected.
-   (merge 11f9e8de3d ds/midx-normalize-pathname-before-comparison later to maint).
-
- * Correct choices of C compilers used in various CI jobs.
-   (merge 3506cae04f ab/cc-package-fixes later to maint).
-
- * Various cleanups to "git p4".
-   (merge 4ff0108d9e jh/p4-various-fixups later to maint).
-
- * The progress meter of "git blame" was showing incorrect numbers
-   when processing only parts of the file.
-   (merge e5f5d7d42e ea/progress-partial-blame later to maint).
-
- * "git rebase --keep-base <upstream> <branch-to-rebase>" computed the
-   commit to rebase onto incorrectly, which has been corrected.
-   (merge 9e5ebe9668 ah/rebase-keep-base-fix later to maint).
-
- * Fix a leak of FILE * in an error codepath.
-   (merge c0befa0c03 kt/commit-graph-plug-fp-leak-on-error later to maint).
-
- * Avoid problems from interaction between malloc_check and address
-   sanitizer.
-   (merge 067109a5e7 pw/test-malloc-with-sanitize-address later to maint).
-
- * The commit summary shown after making a commit is matched to what
-   is given in "git status" not to use the break-rewrite heuristics.
-   (merge 84792322ed rs/commit-summary-wo-break-rewrite later to maint).
-
- * Update a few end-user facing messages around EOL conversion.
-   (merge c970d30c2c ah/convert-warning-message later to maint).
-
- * Trace2 documentation updates.
-   (merge a6c80c313c js/trace2-doc-fixes later to maint).
-
- * Build procedure fixup.
-   (merge 1fbfd96f50 mg/detect-compiler-in-c-locale later to maint).
-
- * "git pull" without "--recurse-submodules=<arg>" made
-   submodule.recurse take precedence over fetch.recurseSubmodules by
-   mistake, which has been corrected.
-   (merge 5819417365 gc/pull-recurse-submodules later to maint).
-
- * "git bisect" was too silent before it is ready to start computing
-   the actual bisection, which has been corrected.
-   (merge f11046e6de cd/bisect-messages-from-pre-flight-states later to maint).
-
- * macOS CI jobs have been occasionally flaky due to tentative version
-   skew between perforce and the homebrew packager.  Instead of
-   failing the whole CI job, just let it skip the p4 tests when this
-   happens.
-   (merge f15e00b463 cb/ci-make-p4-optional later to maint).
-
- * A bit of test framework fixes with a few fixes to issues found by
-   valgrind.
-   (merge 7c898554d7 ab/valgrind-fixes later to maint).
-
- * "git archive --add-file=<path>" picked up the raw permission bits
-   from the path and propagated to zip output in some cases, without
-   normalization, which has been corrected (tar output did not have
-   this issue).
-   (merge 6a61661967 jc/archive-add-file-normalize-mode later to maint).
-
- * "make coverage-report" without first running "make coverage" did
-   not produce any meaningful result, which has been corrected.
-   (merge 96ddfecc5b ep/coverage-report-wants-test-to-have-run later to maint).
-
- * The "--current" option of "git show-branch" should have been made
-   incompatible with the "--reflog" mode, but this was not enforced,
-   which has been corrected.
-   (merge 41c64ae0e7 jc/show-branch-g-current later to maint).
-
- * "git fetch" unnecessarily failed when an unexpected optional
-   section appeared in the output, which has been corrected.
-   (merge 7709acf7be jt/fetch-peek-optional-section later to maint).
-
- * The way "git fetch" without "--update-head-ok" ensures that HEAD in
-   no worktree points at any ref being updated was too wasteful, which
-   has been optimized a bit.
-   (merge f7400da800 os/fetch-check-not-current-branch later to maint).
-
- * "git fetch --recurse-submodules" from multiple remotes (either from
-   a remote group, or "--all") used to make one extra "git fetch" in
-   the submodules, which has been corrected.
-   (merge 0353c68818 jc/avoid-redundant-submodule-fetch later to maint).
-
- * With a recent update to refuse access to repositories of other
-   people by default, "sudo make install" and "sudo git describe"
-   stopped working, which has been corrected.
-   (merge 6b11e3d52e cb/path-owner-check-with-sudo-plus later to maint).
-
- * The tests that ensured merges stop when interfering local changes
-   are present did not make sure that local changes are preserved; now
-   they do.
-   (merge 4b317450ce jc/t6424-failing-merge-preserve-local-changes later to maint).
-
- * Some real problems noticed by gcc 12 have been fixed, while false
-   positives have been worked around.
-
- * Update the version of FreeBSD image used in Cirrus CI.
-   (merge c58bebd4c6 pb/use-freebsd-12.3-in-cirrus-ci later to maint).
-
- * The multi-pack-index code did not protect the packfile it is going
-   to depend on from getting removed while in use, which has been
-   corrected.
-   (merge 4090511e40 tb/midx-race-in-pack-objects later to maint).
-
- * Teach "git repack --geometric" work better with "--keep-pack" and
-   avoid corrupting the repository when packsize limit is used.
-   (merge 66731ff921 tb/geom-repack-with-keep-and-max later to maint).
-
- * The documentation on the interaction between "--add-file" and
-   "--prefix" options of "git archive" has been improved.
-   (merge a75910602a rs/document-archive-prefix later to maint).
-
- * A git subcommand like "git add -p" spawns a separate git process
-   while relaying its command line arguments.  A pathspec with only
-   negative elements was mistakenly passed with an empty string, which
-   has been corrected.
-   (merge b02fdbc80a jc/all-negative-pathspec later to maint).
-
- * With a more targeted workaround in http.c in another topic, we may
-   be able to lift this blanket "GCC12 dangling-pointer warning is
-   broken and unsalvageable" workaround.
-   (merge 419141e495 cb/buggy-gcc-12-workaround later to maint).
-
- * A misconfigured 'branch..remote' led to a bug in configuration
-   parsing.
-   (merge f1dfbd9ee0 gc/zero-length-branch-config-fix later to maint).
-
- * "git -c diff.submodule=log range-diff" did not show anything for
-   submodules that changed in the ranges being compared, and
-   "git -c diff.submodule=diff range-diff" did not work correctly.
-   Fix this by including the "--submodule=short" output
-   unconditionally to be compared.
-
- * In Git 2.36 we revamped the way how hooks are invoked.  One change
-   that is end-user visible is that the output of a hook is no longer
-   directly connected to the standard output of "git" that spawns the
-   hook, which was noticed post release.  This is getting corrected.
-   (merge a082345372 ab/hooks-regression-fix later to maint).
-
- * Updating the graft information invalidates the list of parents of
-   in-core commit objects that used to be in the graft file.
-
- * "git show-ref --heads" (and "--tags") still iterated over all the
-   refs only to discard refs outside the specified area, which has
-   been corrected.
-   (merge c0c9d35e27 tb/show-ref-optim later to maint).
-
- * Remove redundant copying (with index v3 and older) or possible
-   over-reading beyond end of mmapped memory (with index v4) has been
-   corrected.
-   (merge 6d858341d2 zh/read-cache-copy-name-entry-fix later to maint).
-
- * Sample watchman interface hook sometimes failed to produce
-   correctly formatted JSON message, which has been corrected.
-   (merge 134047b500 sn/fsmonitor-missing-clock later to maint).
-
- * Use-after-free (with another forget-to-free) fix.
-   (merge 323822c72b ab/remote-free-fix later to maint).
-
- * Remove a coccinelle rule that is no longer relevant.
-   (merge b1299de4a1 jc/cocci-cleanup later to maint).
-
- * Other code cleanup, docfix, build fix, etc.
-   (merge e6b2582da3 cm/reftable-0-length-memset later to maint).
-   (merge 0b75e5bf22 ab/misc-cleanup later to maint).
-   (merge 52e1ab8a76 ea/rebase-code-simplify later to maint).
-   (merge 756d15923b sg/safe-directory-tests-and-docs later to maint).
-   (merge d097a23bfa ds/do-not-call-bug-on-bad-refs later to maint).
-   (merge c36c27e75c rs/t7812-pcre2-ws-bug-test later to maint).
-   (merge 1da312742d gf/unused-includes later to maint).
-   (merge 465b30a92d pb/submodule-recurse-mode-enum later to maint).
-   (merge 82b28c4ed8 km/t3501-use-test-helpers later to maint).
-   (merge 72315e431b sa/t1011-use-helpers later to maint).
-   (merge 95b3002201 cg/vscode-with-gdb later to maint).
-   (merge fbe5f6b804 tk/p4-utf8-bom later to maint).
-   (merge 17f273ffba tk/p4-with-explicity-sync later to maint).
-   (merge 944db25c60 kf/p4-multiple-remotes later to maint).
-   (merge b014cee8de jc/update-ozlabs-url later to maint).
-   (merge 4ec5008062 pb/ggg-in-mfc-doc later to maint).
-   (merge af845a604d tb/receive-pack-code-cleanup later to maint).
-   (merge 2acf4cf001 js/ci-gcc-12-fixes later to maint).
-   (merge 05e280c0a6 jc/http-clear-finished-pointer later to maint).
-   (merge 8c49d704ef fh/transport-push-leakfix later to maint).
-   (merge 1d232d38bd tl/ls-tree-oid-only later to maint).
-   (merge db7961e6a6 gc/document-config-worktree-scope later to maint).
-   (merge ce18a30bb7 fs/ssh-default-key-command-doc later to maint).

Documentation/SubmittingPatches

@@ -19,10 +19,8 @@ change is relevant to.
   base your work on the tip of the topic.
 
 * A new feature should be based on `master` in general. If the new
-  feature depends on other topics that are in `next`, but not in
-  `master`, fork a branch from the tip of `master`, merge these topics
-  to the branch, and work on that branch.  You can remind yourself of
-  how you prepared the base with `git log --first-parent master..`.
+  feature depends on a topic that is in `seen`, but not in `master`,
+  base your work on the tip of that topic.
 
 * Corrections and enhancements to a topic not yet in `master` should
   be based on the tip of that topic. If the topic has not been merged
@@ -30,10 +28,10 @@ change is relevant to.
   into the series.
 
 * In the exceptional case that a new feature depends on several topics
-  not in `master`, start working on `next` or `seen` privately and
-  send out patches only for discussion. Once your new feature starts
-  to stabilize, you would have to rebase it (see the "depends on other
-  topics" above).
+  not in `master`, start working on `next` or `seen` privately and send
+  out patches for discussion. Before the final merge, you may have to
+  wait until some of the dependent topics graduate to `master`, and
+  rebase your work.
 
 * Some parts of the system have dedicated maintainers with their own
   repositories (see the section "Subsystems" below).  Changes to
@@ -73,13 +71,8 @@ Make sure that you have tests for the bug you are fixing.  See
 [[tests]]
 When adding a new feature, make sure that you have new tests to show
 the feature triggers the new behavior when it should, and to show the
-feature does not trigger when it shouldn't.  After any code change,
-make sure that the entire test suite passes.  When fixing a bug, make
-sure you have new tests that break if somebody else breaks what you
-fixed by accident to avoid regression.  Also, try merging your work to
-'next' and 'seen' and make sure the tests still pass; topics by others
-that are still in flight may have unexpected interactions with what
-you are trying to do in your topic.
+feature does not trigger when it shouldn't.  After any code change, make
+sure that the entire test suite passes.
 
 Pushing to a fork of https://github.com/git/git will use their CI
 integration to test your changes on Linux, Mac and Windows. See the
@@ -110,35 +103,6 @@ run `git diff --check` on your changes before you commit.
 [[describe-changes]]
 === Describe your changes well.
 
-The log message that explains your changes is just as important as the
-changes themselves.  Your code may be clearly written with in-code
-comment to sufficiently explain how it works with the surrounding
-code, but those who need to fix or enhance your code in the future
-will need to know _why_ your code does what it does, for a few
-reasons:
-
-. Your code may be doing something differently from what you wanted it
-  to do.  Writing down what you actually wanted to achieve will help
-  them fix your code and make it do what it should have been doing
-  (also, you often discover your own bugs yourself, while writing the
-  log message to summarize the thought behind it).
-
-. Your code may be doing things that were only necessary for your
-  immediate needs (e.g. "do X to directories" without implementing or
-  even designing what is to be done on files).  Writing down why you
-  excluded what the code does not do will help guide future developers.
-  Writing down "we do X to directories, because directories have
-  characteristic Y" would help them infer "oh, files also have the same
-  characteristic Y, so perhaps doing X to them would also make sense?".
-  Saying "we don't do the same X to files, because ..." will help them
-  decide if the reasoning is sound (in which case they do not waste
-  time extending your code to cover files), or reason differently (in
-  which case, they can explain why they extend your code to cover
-  files, too).
-
-The goal of your log message is to convey the _why_ behind your
-change to help future developers.
-
 The first line of the commit message should be a short description (50
 characters is the soft limit, see DISCUSSION in linkgit:git-commit[1]),
 and should skip the full stop.  It is also conventional in most cases to
@@ -171,13 +135,6 @@ The body should provide a meaningful commit message, which:
 
 . alternate solutions considered but discarded, if any.
 
-[[present-tense]]
-The problem statement that describes the status quo is written in the
-present tense.  Write "The code does X when it is given input Y",
-instead of "The code used to do Y when given input X".  You do not
-have to say "Currently"---the status quo in the problem statement is
-about the code _without_ your change, by project convention.
-
 [[imperative-mood]]
 Describe your changes in imperative mood, e.g. "make xyzzy do frotz"
 instead of "[This patch] makes xyzzy do frotz" or "[I] changed xyzzy
@@ -187,21 +144,8 @@ without external resources. Instead of giving a URL to a mailing list
 archive, summarize the relevant points of the discussion.
 
 [[commit-reference]]
-
-There are a few reasons why you may want to refer to another commit in
-the "more stable" part of the history (i.e. on branches like `maint`,
-`master`, and `next`):
-
-. A commit that introduced the root cause of a bug you are fixing.
-
-. A commit that introduced a feature that you are enhancing.
-
-. A commit that conflicts with your work when you made a trial merge
-  of your work into `next` and `seen` for testing.
-
-When you reference a commit on a more stable branch (like `master`,
-`maint` and `next`), use the format "abbreviated hash (subject,
-date)", like this:
+If you want to reference a previous commit in the history of a stable
+branch, use the format "abbreviated hash (subject, date)", like this:
 
 ....
 	Commit f86a374 (pack-bitmap.c: fix a memleak, 2015-03-30)
@@ -315,11 +259,9 @@ Please make sure your patch does not add commented out debugging code,
 or include any extra files which do not relate to what your patch
 is trying to achieve. Make sure to review
 your patch after generating it, to ensure accuracy.  Before
-sending out, please make sure it cleanly applies to the base you
-have chosen in the "Decide what to base your work on" section,
-and unless it targets the `master` branch (which is the default),
-mark your patches as such.
-
+sending out, please make sure it cleanly applies to the `master`
+branch head.  If you are preparing a work based on "next" branch,
+that is fine, but please mark it as such.
 
 [[send-patches]]
 === Sending your patches.
@@ -423,10 +365,7 @@ Security mailing list{security-ml-ref}.
 Send your patch with "To:" set to the mailing list, with "cc:" listing
 people who are involved in the area you are touching (the `git
 contacts` command in `contrib/contacts/` can help to
-identify them), to solicit comments and reviews.  Also, when you made
-trial merges of your topic to `next` and `seen`, you may have noticed
-work by others conflicting with your changes.  There is a good possibility
-that these people may know the area you are touching well.
+identify them), to solicit comments and reviews.
 
 :current-maintainer: footnote:[The current maintainer: gitster@pobox.com]
 :git-ml: footnote:[The mailing list: git@vger.kernel.org]
@@ -452,10 +391,7 @@ repositories.
 
 - `gitk-git/` comes from Paul Mackerras's gitk project:
 
-	git://git.ozlabs.org/~paulus/gitk
-
-   Those who are interested in improve gitk can volunteer to help Paul
-   in maintaining it cf. <YntxL/fTplFm8lr6@cleo>.
+	git://ozlabs.org/~paulus/gitk
 
 - `po/` comes from the localization coordinator, Jiang Xin:
 
@@ -512,7 +448,7 @@ their trees themselves.
   entitled "What's cooking in git.git" and "What's in git.git" giving
   the status of various proposed changes.
 
-== GitHub CI[[GHCI]]
+== GitHub CI[[GHCI]]]
 
 With an account at GitHub, you can use GitHub CI to test your changes
 on Linux, Mac and Windows. See
@@ -527,7 +463,7 @@ Follow these steps for the initial setup:
 
 After the initial setup, CI will run whenever you push new changes
 to your fork of Git on GitHub.  You can monitor the test state of all your
-branches here: `https://github.com/<Your GitHub handle>/git/actions/workflows/main.yml`
+branches here: https://github.com/<Your GitHub handle>/git/actions/workflows/main.yml
 
 If a branch did not pass all test cases then it is marked with a red
 cross. In that case you can click on the failing job and navigate to

Documentation/ToolsForGit.txt

@@ -1,51 +0,0 @@
-Tools for developing Git
-========================
-:sectanchors:
-
-[[summary]]
-== Summary
-
-This document gathers tips, scripts and configuration file to help people
-working on Git's codebase use their favorite tools while following Git's
-coding style.
-
-[[author]]
-=== Author
-
-The Git community.
-
-[[table_of_contents]]
-== Table of contents
-
-- <<vscode>>
-- <<emacs>>
-
-[[vscode]]
-=== Visual Studio Code (VS Code)
-
-The contrib/vscode/init.sh script creates configuration files that enable
-several valuable VS Code features. See contrib/vscode/README.md for more
-information on using the script.
-
-[[emacs]]
-=== Emacs
-
-This is adapted from Linux's suggestion in its CodingStyle document:
-
-- To follow rules of the CodingGuideline, it's useful to put the following in
-GIT_CHECKOUT/.dir-locals.el, assuming you use cperl-mode:
-----
-;; note the first part is useful for C editing, too
-((nil . ((indent-tabs-mode . t)
-	 (tab-width . 8)
-	 (fill-column . 80)))
-	 (cperl-mode . ((cperl-indent-level . 8)
-			(cperl-extra-newline-before-brace . nil)
-			(cperl-merge-trailing-else . t))))
-----
-
-For a more complete setup, since Git's codebase uses a coding style
-similar to the Linux kernel's style, tips given in Linux's CodingStyle
-document can be applied here too.
-
-==== https://www.kernel.org/doc/html/v4.10/process/coding-style.html#you-ve-made-a-mess-of-it

Documentation/blame-options.txt

@@ -136,16 +136,5 @@ take effect.
 	option.  An empty file name, `""`, will clear the list of revs from
 	previously processed files.
 
---color-lines::
-	Color line annotations in the default format differently if they come from
-	the same commit as the preceding line. This makes it easier to distinguish
-	code blocks introduced by different commits. The color defaults to cyan and
-	can be adjusted using the `color.blame.repeatedLines` config option.
-
---color-by-age::
-	Color line annotations depending on the age of the line in the default format.
-	The `color.blame.highlightRecent` config option controls what color is used for
-	each range of age.
-
 -h::
 	Show help message.

Documentation/config.txt

@@ -159,33 +159,6 @@ all branches that begin with `foo/`. This is useful if your branches are
 organized hierarchically and you would like to apply a configuration to
 all the branches in that hierarchy.
 
-`hasconfig:remote.*.url:`::
-	The data that follows this keyword is taken to
-	be a pattern with standard globbing wildcards and two
-	additional ones, `**/` and `/**`, that can match multiple
-	components. The first time this keyword is seen, the rest of
-	the config files will be scanned for remote URLs (without
-	applying any values). If there exists at least one remote URL
-	that matches this pattern, the include condition is met.
-+
-Files included by this option (directly or indirectly) are not allowed
-to contain remote URLs.
-+
-Note that unlike other includeIf conditions, resolving this condition
-relies on information that is not yet known at the point of reading the
-condition. A typical use case is this option being present as a
-system-level or global-level config, and the remote URL being in a
-local-level config; hence the need to scan ahead when resolving this
-condition. In order to avoid the chicken-and-egg problem in which
-potentially-included files can affect whether such files are potentially
-included, Git breaks the cycle by prohibiting these files from affecting
-the resolution of these conditions (thus, prohibiting them from
-declaring remote URLs).
-+
-As for the naming of this keyword, it is for forwards compatibiliy with
-a naming scheme that supports more variable-based include conditions,
-but currently Git only supports the exact keyword described above.
-
 A few more notes on matching via `gitdir` and `gitdir/i`:
 
  * Symlinks in `$GIT_DIR` are not resolved before matching.
@@ -253,14 +226,6 @@ Example
 ; currently checked out
 [includeIf "onbranch:foo-branch"]
 	path = foo.inc
-
-; include only if a remote with the given URL exists (note
-; that such a URL may be provided later in a file or in a
-; file read after this file is read, as seen in this example)
-[includeIf "hasconfig:remote.*.url:https://example.com/**"]
-	path = foo.inc
-[remote "origin"]
-	url = https://example.com/git
 ----
 
 Values
@@ -297,19 +262,11 @@ color::
        colors (at most two, one for foreground and one for background)
        and attributes (as many as you want), separated by spaces.
 +
-The basic colors accepted are `normal`, `black`, `red`, `green`,
-`yellow`, `blue`, `magenta`, `cyan`, `white` and `default`.  The first
-color given is the foreground; the second is the background.  All the
-basic colors except `normal` and `default` have a bright variant that can
-be specified by prefixing the color with `bright`, like `brightred`.
-+
-The color `normal` makes no change to the color. It is the same as an
-empty string, but can be used as the foreground color when specifying a
-background color alone (for example, "normal red").
-+
-The color `default` explicitly resets the color to the terminal default,
-for example to specify a cleared background. Although it varies between
-terminals, this is usually not the same as setting to "white black".
+The basic colors accepted are `normal`, `black`, `red`, `green`, `yellow`,
+`blue`, `magenta`, `cyan` and `white`.  The first color given is the
+foreground; the second is the background.  All the basic colors except
+`normal` have a bright variant that can be specified by prefixing the
+color with `bright`, like `brightred`.
 +
 Colors may also be given as numbers between 0 and 255; these use ANSI
 256-color mode (but note that not all terminals may support this).  If
@@ -323,11 +280,6 @@ The position of any attributes with respect to the colors
 be turned off by prefixing them with `no` or `no-` (e.g., `noreverse`,
 `no-ul`, etc).
 +
-The pseudo-attribute `reset` resets all colors and attributes before
-applying the specified coloring. For example, `reset green` will result
-in a green foreground and default background without any active
-attributes.
-+
 An empty color string produces no color effect at all. This can be used
 to avoid coloring specific elements without disabling color entirely.
 +
@@ -346,15 +298,6 @@ pathname::
 	tilde expansion happens to such a string: `~/`
 	is expanded to the value of `$HOME`, and `~user/` to the
 	specified user's home directory.
-+
-If a path starts with `%(prefix)/`, the remainder is interpreted as a
-path relative to Git's "runtime prefix", i.e. relative to the location
-where Git itself was installed. For example, `%(prefix)/bin/` refers to
-the directory in which the Git executable itself lives. If Git was
-compiled without runtime prefix support, the compiled-in prefix will be
-substituted instead. In the unlikely event that a literal path needs to
-be specified that should _not_ be expanded, it needs to be prefixed by
-`./`, like so: `./%(prefix)/bin`.
 
 
 Variables
@@ -495,6 +438,8 @@ include::config/repack.txt[]
 
 include::config/rerere.txt[]
 
+include::config/reset.txt[]
+
 include::config/safe.txt[]
 
 include::config/sendemail.txt[]
@@ -503,8 +448,6 @@ include::config/sequencer.txt[]
 
 include::config/showbranch.txt[]
 
-include::config/sparse.txt[]
-
 include::config/splitindex.txt[]
 
 include::config/ssh.txt[]

Documentation/config/add.txt

@@ -7,6 +7,6 @@ add.ignore-errors (deprecated)::
 	variables.
 
 add.interactive.useBuiltin::
-	Set to `false` to fall back to the original Perl implementation of
-	the interactive version of linkgit:git-add[1] instead of the built-in
-	version. Is `true` by default.
+	[EXPERIMENTAL] Set to `true` to use the experimental built-in
+	implementation of the interactive version of linkgit:git-add[1]
+	instead of the Perl script version. Is `false` by default.

Documentation/config/advice.txt

@@ -4,10 +4,6 @@ advice.*::
 	can tell Git that you do not need help by setting these to 'false':
 +
 --
-	ambiguousFetchRefspec::
-		Advice shown when fetch refspec for multiple remotes map to
-		the same remote-tracking branch namespace and causes branch
-		tracking set-up to fail.
 	fetchShowForcedUpdates::
 		Advice shown when linkgit:git-fetch[1] takes a long time
 		to calculate forced updates after ref updates, or to warn
@@ -48,9 +44,6 @@ advice.*::
 		Shown when linkgit:git-push[1] rejects a forced update of
 		a branch when its remote-tracking ref has updates that we
 		do not have locally.
-	skippedCherryPicks::
-		Shown when linkgit:git-rebase[1] skips a commit that has already
-		been cherry-picked onto the upstream branch.
 	statusAheadBehind::
 		Shown when linkgit:git-status[1] computes the ahead/behind
 		counts for a local ref compared to its remote tracking ref,
@@ -71,10 +64,10 @@ advice.*::
 	commitBeforeMerge::
 		Advice shown when linkgit:git-merge[1] refuses to
 		merge to avoid overwriting local changes.
-	resetNoRefresh::
-		Advice to consider using the `--no-refresh` option to
-		linkgit:git-reset[1] when the command takes more than 2 seconds
-		to refresh the index after reset.
+	resetQuiet::
+		Advice to consider using the `--quiet` option to linkgit:git-reset[1]
+		when the command takes more than 2 seconds to enumerate unstaged
+		changes after reset.
 	resolveConflict::
 		Advice shown by various commands when conflicts
 		prevent the operation from being performed.
@@ -89,9 +82,6 @@ advice.*::
 		linkgit:git-switch[1] or linkgit:git-checkout[1]
 		to move to the detach HEAD state, to instruct how to
 		create a local branch after the fact.
-	suggestDetachingHead::
-		Advice shown when linkgit:git-switch[1] refuses to detach HEAD
-		without the explicit `--detach` option.
 	checkoutAmbiguousRemoteBranchName::
 		Advice shown when the argument to
 		linkgit:git-checkout[1] and linkgit:git-switch[1]
@@ -123,9 +113,6 @@ advice.*::
 	submoduleAlternateErrorStrategyDie::
 		Advice shown when a submodule.alternateErrorStrategy option
 		configured to "die" causes a fatal error.
-	submodulesNotUpdated::
-		Advice shown when a user runs a submodule command that fails
-		because `git submodule update --init` was not run.
 	addIgnoredFile::
 		Advice shown if a user attempts to add an ignored file to
 		the index.

Documentation/config/branch.txt

@@ -7,11 +7,8 @@ branch.autoSetupMerge::
 	automatic setup is done; `true` -- automatic setup is done when the
 	starting point is a remote-tracking branch; `always` --
 	automatic setup is done when the starting point is either a
-	local branch or remote-tracking branch; `inherit` -- if the starting point
-	has a tracking configuration, it is copied to the new
-	branch; `simple` -- automatic setup is done only when the starting point
-	is a remote-tracking branch and the new branch has the same name as the
-	remote branch. This option defaults to true.
+	local branch or remote-tracking
+	branch. This option defaults to true.
 
 branch.autoSetupRebase::
 	When a new branch is created with 'git branch', 'git switch' or 'git checkout'
@@ -40,9 +37,8 @@ branch.<name>.remote::
 	may be overridden with `remote.pushDefault` (for all branches).
 	The remote to push to, for the current branch, may be further
 	overridden by `branch.<name>.pushRemote`.  If no remote is
-	configured, or if you are not on any branch and there is more than
-	one remote defined in the repository, it defaults to `origin` for
-	fetching and `remote.pushDefault` for pushing.
+	configured, or if you are not on any branch, it defaults to
+	`origin` for fetching and `remote.pushDefault` for pushing.
 	Additionally, `.` (a period) is the current local repository
 	(a dot-repository), see `branch.<name>.merge`'s final note below.
 
@@ -89,6 +85,10 @@ When `merges` (or just 'm'), pass the `--rebase-merges` option to 'git rebase'
 so that the local merge commits are included in the rebase (see
 linkgit:git-rebase[1] for details).
 +
+When `preserve` (or just 'p', deprecated in favor of `merges`), also pass
+`--preserve-merges` along to 'git rebase' so that locally committed merge
+commits will not be flattened by running 'git pull'.
++
 When the value is `interactive` (or just 'i'), the rebase is run in interactive
 mode.
 +

Documentation/config/clone.txt

@@ -6,8 +6,3 @@ clone.defaultRemoteName::
 clone.rejectShallow::
 	Reject to clone a repository if it is a shallow one, can be overridden by
 	passing option `--reject-shallow` in command line. See linkgit:git-clone[1]
-
-clone.filterSubmodules::
-	If a partial clone filter is provided (see `--filter` in
-	linkgit:git-rev-list[1]) and `--recurse-submodules` is used, also apply
-	the filter to submodules.

Documentation/config/color.txt

@@ -9,27 +9,26 @@ color.advice.hint::
 	Use customized color for hints.
 
 color.blame.highlightRecent::
-	Specify the line annotation color for `git blame --color-by-age`
-	depending upon the age of the line.
+	This can be used to color the metadata of a blame line depending
+	on age of the line.
 +
-This setting should be set to a comma-separated list of color and
-date settings, starting and ending with a color, the dates should be
-set from oldest to newest. The metadata will be colored with the
-specified colors if the line was introduced before the given
-timestamp, overwriting older timestamped colors.
+This setting should be set to a comma-separated list of color and date settings,
+starting and ending with a color, the dates should be set from oldest to newest.
+The metadata will be colored given the colors if the line was introduced
+before the given timestamp, overwriting older timestamped colors.
 +
-Instead of an absolute timestamp relative timestamps work as well,
-e.g. `2.weeks.ago` is valid to address anything older than 2 weeks.
+Instead of an absolute timestamp relative timestamps work as well, e.g.
+2.weeks.ago is valid to address anything older than 2 weeks.
 +
-It defaults to `blue,12 month ago,white,1 month ago,red`, which
-colors everything older than one year blue, recent changes between
-one month and one year old are kept white, and lines introduced
-within the last month are colored red.
+It defaults to 'blue,12 month ago,white,1 month ago,red', which colors
+everything older than one year blue, recent changes between one month and
+one year old are kept white, and lines introduced within the last month are
+colored red.
 
 color.blame.repeatedLines::
-	Use the specified color to colorize line annotations for
-	`git blame --color-lines`, if they come from the same commit as the
-	preceding line. Defaults to cyan.
+	Use the customized color for the part of git-blame output that
+	is repeated meta information per line (such as commit id,
+	author name, date and timezone). Defaults to cyan.
 
 color.branch::
 	A boolean to enable/disable color in the output of
@@ -105,12 +104,9 @@ color.grep.<slot>::
 `matchContext`;;
 	matching text in context lines
 `matchSelected`;;
-	matching text in selected lines. Also, used to customize the following
-	linkgit:git-log[1] subcommands: `--grep`, `--author` and `--committer`.
+	matching text in selected lines
 `selected`;;
-	non-matching text in selected lines. Also, used to customize the
-	following linkgit:git-log[1] subcommands: `--grep`, `--author` and
-	`--committer`.
+	non-matching text in selected lines
 `separator`;;
 	separators between fields on a line (`:`, `-`, and `=`)
 	and between hunks (`--`)

Documentation/config/core.txt

@@ -62,54 +62,22 @@ core.protectNTFS::
 	Defaults to `true` on Windows, and `false` elsewhere.
 
 core.fsmonitor::
-	If set to true, enable the built-in file system monitor
-	daemon for this working directory (linkgit:git-fsmonitor{litdd}daemon[1]).
-+
-Like hook-based file system monitors, the built-in file system monitor
-can speed up Git commands that need to refresh the Git index
-(e.g. `git status`) in a working directory with many files.  The
-built-in monitor eliminates the need to install and maintain an
-external third-party tool.
-+
-The built-in file system monitor is currently available only on a
-limited set of supported platforms.  Currently, this includes Windows
-and MacOS.
-+
-	Otherwise, this variable contains the pathname of the "fsmonitor"
-	hook command.
-+
-This hook command is used to identify all files that may have changed
-since the requested date/time. This information is used to speed up
-git by avoiding unnecessary scanning of files that have not changed.
-+
-See the "fsmonitor-watchman" section of linkgit:githooks[5].
-+
-Note that if you concurrently use multiple versions of Git, such
-as one version on the command line and another version in an IDE
-tool, that the definition of `core.fsmonitor` was extended to
-allow boolean values in addition to hook pathnames.  Git versions
-2.35.1 and prior will not understand the boolean values and will
-consider the "true" or "false" values as hook pathnames to be
-invoked.  Git versions 2.26 thru 2.35.1 default to hook protocol
-V2 and will fall back to no fsmonitor (full scan).  Git versions
-prior to 2.26 default to hook protocol V1 and will silently
-assume there were no changes to report (no scan), so status
-commands may report incomplete results.  For this reason, it is
-best to upgrade all of your Git versions before using the built-in
-file system monitor.
+	If set, the value of this variable is used as a command which
+	will identify all files that may have changed since the
+	requested date/time. This information is used to speed up git by
+	avoiding unnecessary processing of files that have not changed.
+	See the "fsmonitor-watchman" section of linkgit:githooks[5].
 
 core.fsmonitorHookVersion::
-	Sets the protocol version to be used when invoking the
-	"fsmonitor" hook.
-+
-There are currently versions 1 and 2. When this is not set,
-version 2 will be tried first and if it fails then version 1
-will be tried. Version 1 uses a timestamp as input to determine
-which files have changes since that time but some monitors
-like Watchman have race conditions when used with a timestamp.
-Version 2 uses an opaque string so that the monitor can return
-something that can be used to determine what files have changed
-without race conditions.
+	Sets the version of hook that is to be used when calling fsmonitor.
+	There are currently versions 1 and 2. When this is not set,
+	version 2 will be tried first and if it fails then version 1
+	will be tried. Version 1 uses a timestamp as input to determine
+	which files have changes since that time but some monitors
+	like watchman have race conditions when used with a timestamp.
+	Version 2 uses an opaque string so that the monitor can return
+	something that can be used to determine what files have changed
+	without race conditions.
 
 core.trustctime::
 	If false, the ctime differences between the index and the
@@ -579,72 +547,13 @@ core.whitespace::
   is relevant for `indent-with-non-tab` and when Git fixes `tab-in-indent`
   errors. The default tab width is 8. Allowed values are 1 to 63.
 
-core.fsync::
-	A comma-separated list of components of the repository that
-	should be hardened via the core.fsyncMethod when created or
-	modified.  You can disable hardening of any component by
-	prefixing it with a '-'.  Items that are not hardened may be
-	lost in the event of an unclean	system shutdown. Unless you
-	have special requirements, it is recommended that you leave
-	this option empty or pick one of `committed`, `added`,
-	or `all`.
-+
-When this configuration is encountered, the set of components starts with
-the platform default value, disabled components are removed, and additional
-components are added. `none` resets the state so that the platform default
-is ignored.
-+
-The empty string resets the fsync configuration to the platform
-default. The default on most platforms is equivalent to
-`core.fsync=committed,-loose-object`, which has good performance,
-but risks losing recent work in the event of an unclean system shutdown.
-+
-* `none` clears the set of fsynced components.
-* `loose-object` hardens objects added to the repo in loose-object form.
-* `pack` hardens objects added to the repo in packfile form.
-* `pack-metadata` hardens packfile bitmaps and indexes.
-* `commit-graph` hardens the commit graph file.
-* `index` hardens the index when it is modified.
-* `objects` is an aggregate option that is equivalent to
-  `loose-object,pack`.
-* `reference` hardens references modified in the repo.
-* `derived-metadata` is an aggregate option that is equivalent to
-  `pack-metadata,commit-graph`.
-* `committed` is an aggregate option that is currently equivalent to
-  `objects`. This mode sacrifices some performance to ensure that work
-  that is committed to the repository with `git commit` or similar commands
-  is hardened.
-* `added` is an aggregate option that is currently equivalent to
-  `committed,index`. This mode sacrifices additional performance to
-  ensure that the results of commands like `git add` and similar operations
-  are hardened.
-* `all` is an aggregate option that syncs all individual components above.
-
-core.fsyncMethod::
-	A value indicating the strategy Git will use to harden repository data
-	using fsync and related primitives.
-+
-* `fsync` uses the fsync() system call or platform equivalents.
-* `writeout-only` issues pagecache writeback requests, but depending on the
-  filesystem and storage hardware, data added to the repository may not be
-  durable in the event of a system crash. This is the default mode on macOS.
-* `batch` enables a mode that uses writeout-only flushes to stage multiple
-  updates in the disk writeback cache and then does a single full fsync of
-  a dummy file to trigger the disk cache flush at the end of the operation.
-+
-Currently `batch` mode only applies to loose-object files. Other repository
-data is made durable as if `fsync` was specified. This mode is expected to
-be as safe as `fsync` on macOS for repos stored on HFS+ or APFS filesystems
-and on Windows for repos stored on NTFS or ReFS filesystems.
-
 core.fsyncObjectFiles::
 	This boolean will enable 'fsync()' when writing object files.
-	This setting is deprecated. Use core.fsync instead.
 +
-This setting affects data added to the Git repository in loose-object
-form. When set to true, Git will issue an fsync or similar system call
-to flush caches so that loose-objects remain consistent in the face
-of a unclean system shutdown.
+This is a total waste of time and effort on a filesystem that orders
+data writes properly, but can be useful for filesystems that do not use
+journalling (traditional UNIX filesystems) or that only journal metadata
+and not file contents (OS X's HFS+, or Linux ext3 with "data=writeback").
 
 core.preloadIndex::
 	Enable parallel index preload for operations like 'git diff'
@@ -706,10 +615,8 @@ core.sparseCheckout::
 
 core.sparseCheckoutCone::
 	Enables the "cone mode" of the sparse checkout feature. When the
-	sparse-checkout file contains a limited set of patterns, this
-	mode provides significant performance advantages. The "non
-	cone mode" can be requested to allow specifying a more flexible
-	patterns by setting this variable to 'false'. See
+	sparse-checkout file contains a limited set of patterns, then this
+	mode provides significant performance advantages. See
 	linkgit:git-sparse-checkout[1] for more information.
 
 core.abbrev::

Documentation/config/extensions.txt

@@ -6,34 +6,3 @@ extensions.objectFormat::
 Note that this setting should only be set by linkgit:git-init[1] or
 linkgit:git-clone[1].  Trying to change it after initialization will not
 work and will produce hard-to-diagnose issues.
-
-extensions.worktreeConfig::
-	If enabled, then worktrees will load config settings from the
-	`$GIT_DIR/config.worktree` file in addition to the
-	`$GIT_COMMON_DIR/config` file. Note that `$GIT_COMMON_DIR` and
-	`$GIT_DIR` are the same for the main working tree, while other
-	working trees have `$GIT_DIR` equal to
-	`$GIT_COMMON_DIR/worktrees/<id>/`. The settings in the
-	`config.worktree` file will override settings from any other
-	config files.
-+
-When enabling `extensions.worktreeConfig`, you must be careful to move
-certain values from the common config file to the main working tree's
-`config.worktree` file, if present:
-+
-* `core.worktree` must be moved from `$GIT_COMMON_DIR/config` to
-  `$GIT_COMMON_DIR/config.worktree`.
-* If `core.bare` is true, then it must be moved from `$GIT_COMMON_DIR/config`
-  to `$GIT_COMMON_DIR/config.worktree`.
-+
-It may also be beneficial to adjust the locations of `core.sparseCheckout`
-and `core.sparseCheckoutCone` depending on your desire for customizable
-sparse-checkout settings for each worktree. By default, the `git
-sparse-checkout` builtin enables `extensions.worktreeConfig`, assigns
-these config values on a per-worktree basis, and uses the
-`$GIT_DIR/info/sparse-checkout` file to specify the sparsity for each
-worktree independently. See linkgit:git-sparse-checkout[1] for more
-details.
-+
-For historical reasons, `extensions.worktreeConfig` is respected
-regardless of the `core.repositoryFormatVersion` setting.

Documentation/config/fetch.txt

@@ -56,19 +56,18 @@ fetch.output::
 	OUTPUT in linkgit:git-fetch[1] for detail.
 
 fetch.negotiationAlgorithm::
-	Control how information about the commits in the local repository
-	is sent when negotiating the contents of the packfile to be sent by
-	the server.  Set to "consecutive" to use an algorithm that walks
-	over consecutive commits checking each one.  Set to "skipping" to
-	use an algorithm that skips commits in an effort to converge
-	faster, but may result in a larger-than-necessary packfile; or set
-	to "noop" to not send any information at all, which will almost
-	certainly result in a larger-than-necessary packfile, but will skip
-	the negotiation step.  Set to "default" to override settings made
-	previously and use the default behaviour.  The default is normally
-	"consecutive", but if `feature.experimental` is true, then the
-	default is "skipping".  Unknown values will cause 'git fetch' to
-	error out.
+	Control how information about the commits in the local repository is
+	sent when negotiating the contents of the packfile to be sent by the
+	server. Set to "skipping" to use an algorithm that skips commits in an
+	effort to converge faster, but may result in a larger-than-necessary
+	packfile; or set to "noop" to not send any information at all, which
+	will almost certainly result in a larger-than-necessary packfile, but
+	will skip the negotiation step.
+	The default is "default" which instructs Git to use the default algorithm
+	that never skips commits (unless the server has acknowledged it or one
+	of its descendants). If `feature.experimental` is enabled, then this
+	setting defaults to "skipping".
+	Unknown values will cause 'git fetch' to error out.
 +
 See also the `--negotiate-only` and `--negotiation-tip` options to
 linkgit:git-fetch[1].

Documentation/config/gc.txt

@@ -81,21 +81,14 @@ gc.packRefs::
 	to enable it within all non-bare repos or it can be set to a
 	boolean value.  The default is `true`.
 
-gc.cruftPacks::
-	Store unreachable objects in a cruft pack (see
-	linkgit:git-repack[1]) instead of as loose objects. The default
-	is `false`.
-
 gc.pruneExpire::
-	When 'git gc' is run, it will call 'prune --expire 2.weeks.ago'
-	(and 'repack --cruft --cruft-expiration 2.weeks.ago' if using
-	cruft packs via `gc.cruftPacks` or `--cruft`).  Override the
-	grace period with this config variable.  The value "now" may be
-	used to disable this grace period and always prune unreachable
-	objects immediately, or "never" may be used to suppress pruning.
-	This feature helps prevent corruption when 'git gc' runs
-	concurrently with another process writing to the repository; see
-	the "NOTES" section of linkgit:git-gc[1].
+	When 'git gc' is run, it will call 'prune --expire 2.weeks.ago'.
+	Override the grace period with this config variable.  The value
+	"now" may be used to disable this grace period and always prune
+	unreachable objects immediately, or "never" may be used to
+	suppress pruning.  This feature helps prevent corruption when
+	'git gc' runs concurrently with another process writing to the
+	repository; see the "NOTES" section of linkgit:git-gc[1].
 
 gc.worktreePruneExpire::
 	When 'git gc' is run, it calls

Documentation/config/gpg.txt

@@ -11,13 +11,13 @@ gpg.program::
 
 gpg.format::
 	Specifies which key format to use when signing with `--gpg-sign`.
-	Default is "openpgp". Other possible values are "x509", "ssh".
+	Default is "openpgp" and another possible value is "x509".
 
 gpg.<format>.program::
 	Use this to customize the program used for the signing format you
 	chose. (see `gpg.program` and `gpg.format`) `gpg.program` can still
 	be used as a legacy synonym for `gpg.openpgp.program`. The default
-	value for `gpg.x509.program` is "gpgsm" and `gpg.ssh.program` is "ssh-keygen".
+	value for `gpg.x509.program` is "gpgsm".
 
 gpg.minTrustLevel::
 	Specifies a minimum trust level for signature verification.  If
@@ -33,50 +33,3 @@ gpg.minTrustLevel::
 * `marginal`
 * `fully`
 * `ultimate`
-
-gpg.ssh.defaultKeyCommand::
-	This command that will be run when user.signingkey is not set and a ssh
-	signature is requested. On successful exit a valid ssh public key
-	prefixed with `key::` is expected in the first line of its output.
-	This allows for a script doing a dynamic lookup of the correct public
-	key when it is impractical to statically configure `user.signingKey`.
-	For example when keys or SSH Certificates are rotated frequently or
-	selection of the right key depends on external factors unknown to git.
-
-gpg.ssh.allowedSignersFile::
-	A file containing ssh public keys which you are willing to trust.
-	The file consists of one or more lines of principals followed by an ssh
-	public key.
-	e.g.: `user1@example.com,user2@example.com ssh-rsa AAAAX1...`
-	See ssh-keygen(1) "ALLOWED SIGNERS" for details.
-	The principal is only used to identify the key and is available when
-	verifying a signature.
-+
-SSH has no concept of trust levels like gpg does. To be able to differentiate
-between valid signatures and trusted signatures the trust level of a signature
-verification is set to `fully` when the public key is present in the allowedSignersFile.
-Otherwise the trust level is `undefined` and git verify-commit/tag will fail.
-+
-This file can be set to a location outside of the repository and every developer
-maintains their own trust store. A central repository server could generate this
-file automatically from ssh keys with push access to verify the code against.
-In a corporate setting this file is probably generated at a global location
-from automation that already handles developer ssh keys.
-+
-A repository that only allows signed commits can store the file
-in the repository itself using a path relative to the top-level of the working tree.
-This way only committers with an already valid key can add or change keys in the keyring.
-+
-Since OpensSSH 8.8 this file allows specifying a key lifetime using valid-after &
-valid-before options. Git will mark signatures as valid if the signing key was
-valid at the time of the signature's creation. This allows users to change a
-signing key without invalidating all previously made signatures.
-+
-Using a SSH CA key with the cert-authority option
-(see ssh-keygen(1) "CERTIFICATES") is also valid.
-
-gpg.ssh.revocationFile::
-	Either a SSH KRL or a list of revoked public keys (without the principal prefix).
-	See ssh-keygen(1) for details.
-	If a public key is found in this file then it will always be treated
-	as having trust level "never" and signatures will show as invalid.

Documentation/config/grep.txt

@@ -8,8 +8,7 @@ grep.patternType::
 	Set the default matching behavior. Using a value of 'basic', 'extended',
 	'fixed', or 'perl' will enable the `--basic-regexp`, `--extended-regexp`,
 	`--fixed-strings`, or `--perl-regexp` option accordingly, while the
-	value 'default' will use the `grep.extendedRegexp` option to choose
-	between 'basic' and 'extended'.
+	value 'default' will return to the default matching behavior.
 
 grep.extendedRegexp::
 	If set to true, enable `--extended-regexp` option by default. This

Documentation/config/help.txt

@@ -9,15 +9,13 @@ help.format::
 
 help.autoCorrect::
 	If git detects typos and can identify exactly one valid command similar
-	to the error, git will try to suggest the correct command or even
-	run the suggestion automatically. Possible config values are:
-	 - 0 (default): show the suggested command.
-	 - positive number: run the suggested command after specified
-deciseconds (0.1 sec).
-	 - "immediate": run the suggested command immediately.
-	 - "prompt": show the suggestion and prompt for confirmation to run
-the command.
-	 - "never": don't run or show any suggested command.
+	to the error, git will automatically run the intended command after
+	waiting a duration of time defined by this configuration value in
+	deciseconds (0.1 sec).  If this value is 0, the suggested corrections
+	will be shown, but not executed. If it is a negative integer, or
+	"immediate", the suggested command
+	is run immediately. If "never", suggestions are not shown at all. The
+	default value is zero.
 
 help.htmlPath::
 	Specify the path where the HTML documentation resides. File system paths

Documentation/config/http.txt

@@ -98,22 +98,6 @@ http.version::
 	- HTTP/2
 	- HTTP/1.1
 
-http.curloptResolve::
-	Hostname resolution information that will be used first by
-	libcurl when sending HTTP requests.  This information should
-	be in one of the following formats:
-
-	- [+]HOST:PORT:ADDRESS[,ADDRESS]
-	- -HOST:PORT
-
-+
-The first format redirects all requests to the given `HOST:PORT`
-to the provided `ADDRESS`(s). The second format clears all
-previous config values for that `HOST:PORT` combination.  To
-allow easy overriding of all the settings inherited from the
-system config, an empty value will reset all resolution
-information to the empty list.
-
 http.sslVersion::
 	The SSL version to use when negotiating an SSL connection, if you
 	want to force the default.  The available and default version
@@ -203,7 +187,7 @@ http.schannelUseSSLCAInfo::
 	when the `schannel` backend was configured via `http.sslBackend`,
 	unless `http.schannelUseSSLCAInfo` overrides this behavior.
 
-http.pinnedPubkey::
+http.pinnedpubkey::
 	Public key of the https service. It may either be the filename of
 	a PEM or DER encoded public key file or a string starting with
 	'sha256//' followed by the base64 encoded sha256 hash of the

Documentation/config/merge.txt

@@ -4,14 +4,7 @@ merge.conflictStyle::
 	shows a `<<<<<<<` conflict marker, changes made by one side,
 	a `=======` marker, changes made by the other side, and then
 	a `>>>>>>>` marker.  An alternate style, "diff3", adds a `|||||||`
-	marker and the original text before the `=======` marker.  The
-	"merge" style tends to produce smaller conflict regions than diff3,
-	both because of the exclusion of the original text, and because
-	when a subset of lines match on the two sides they are just pulled
-	out of the conflict region.  Another alternate style, "zdiff3", is
-	similar to diff3 but removes matching lines on the two sides from
-	the conflict region when those matching lines appear near either
-	the beginning or end of a conflict region.
+	marker and the original text before the `=======` marker.
 
 merge.defaultToUpstream::
 	If merge is called without any commit argument, merge the upstream

Documentation/config/mergetool.txt

@@ -45,15 +45,6 @@ mergetool.meld.useAutoMerge::
 	value of `false` avoids using `--auto-merge` altogether, and is the
 	default value.
 
-mergetool.vimdiff.layout::
-	The vimdiff backend uses this variable to control how its split
-	windows look like. Applies even if you are using Neovim (`nvim`) or
-	gVim (`gvim`) as the merge tool. See BACKEND SPECIFIC HINTS section
-ifndef::git-mergetool[]
-	in linkgit:git-mergetool[1].
-endif::[]
-	for details.
-
 mergetool.hideResolved::
 	During a merge Git will automatically resolve as many conflicts as
 	possible and write the 'MERGED' file containing conflict markers around

Documentation/config/pack.txt

@@ -159,10 +159,6 @@ pack.writeBitmapHashCache::
 	between an older, bitmapped pack and objects that have been
 	pushed since the last gc). The downside is that it consumes 4
 	bytes per object of disk space. Defaults to true.
-+
-When writing a multi-pack reachability bitmap, no new namehashes are
-computed; instead, any namehashes stored in an existing bitmap are
-permuted into their appropriate location when writing a new bitmap.
 
 pack.writeReverseIndex::
 	When true, git will write a corresponding .rev file (see:

Documentation/config/protocol.txt

@@ -1,10 +1,10 @@
 protocol.allow::
 	If set, provide a user defined default policy for all protocols which
 	don't explicitly have a policy (`protocol.<name>.allow`).  By default,
-	if unset, known-safe protocols (http, https, git, ssh, file) have a
+	if unset, known-safe protocols (http, https, git, ssh) have a
 	default policy of `always`, known-dangerous protocols (ext) have a
-	default policy of `never`, and all other protocols have a default
-	policy of `user`.  Supported policies:
+	default policy of `never`, and all other protocols (including file)
+	have a default policy of `user`.  Supported policies:
 +
 --
 

Documentation/config/pull.txt

@@ -18,6 +18,10 @@ When `merges` (or just 'm'), pass the `--rebase-merges` option to 'git rebase'
 so that the local merge commits are included in the rebase (see
 linkgit:git-rebase[1] for details).
 +
+When `preserve` (or just 'p', deprecated in favor of `merges`), also pass
+`--preserve-merges` along to 'git rebase' so that locally committed merge
+commits will not be flattened by running 'git pull'.
++
 When the value is `interactive` (or just 'i'), the rebase is run in interactive
 mode.
 +

Documentation/config/push.txt

@@ -1,14 +1,3 @@
-push.autoSetupRemote::
-	If set to "true" assume `--set-upstream` on default push when no
-	upstream tracking exists for the current branch; this option
-	takes effect with push.default options 'simple', 'upstream',
-	and 'current'. It is useful if by default you want new branches
-	to be pushed to the default remote (like the behavior of
-	'push.default=current') and you also want the upstream tracking
-	to be set. Workflows most likely to benefit from this option are
-	'simple' central workflows where all branches are expected to
-	have the same name on the remote.
-
 push.default::
 	Defines the action `git push` should take if no refspec is
 	given (whether from the command-line, config, or elsewhere).

Documentation/config/remote.txt

@@ -82,7 +82,5 @@ remote.<name>.promisor::
 	objects.
 
 remote.<name>.partialclonefilter::
-	The filter that will be applied when fetching from this	promisor remote.
-	Changing or clearing this value will only affect fetches for new commits.
-	To fetch associated objects for commits already present in the local object
-	database, use the `--refetch` option of linkgit:git-fetch[1].
+	The filter that will be applied when fetching from this
+	promisor remote.

Documentation/config/repack.txt

@@ -25,17 +25,3 @@ repack.writeBitmaps::
 	space and extra time spent on the initial repack.  This has
 	no effect if multiple packfiles are created.
 	Defaults to true on bare repos, false otherwise.
-
-repack.updateServerInfo::
-	If set to false, linkgit:git-repack[1] will not run
-	linkgit:git-update-server-info[1]. Defaults to true. Can be overridden
-	when true by the `-n` option of linkgit:git-repack[1].
-
-repack.cruftWindow::
-repack.cruftWindowMemory::
-repack.cruftDepth::
-repack.cruftThreads::
-	Parameters used by linkgit:git-pack-objects[1] when generating
-	a cruft pack and the respective parameters are not given over
-	the command line. See similarly named `pack.*` configuration
-	variables for defaults and meaning.

Documentation/config/reset.txt

@@ -0,0 +1,2 @@
+reset.quiet::
+	When set to true, 'git reset' will default to the '--quiet' option.

Documentation/config/revert.txt

@@ -1,3 +0,0 @@
-revert.reference::
-	Setting this variable to true makes `git revert` to behave
-	as if the `--reference` option is given.

Documentation/config/safe.txt

@@ -13,8 +13,8 @@ override any such directories specified in the system config), add a
 `safe.directory` entry with an empty value.
 +
 This config setting is only respected when specified in a system or global
-config, not when it is specified in a repository config, via the command
-line option `-c safe.directory=<path>`, or in environment variables.
+config, not when it is specified in a repository config or via the command
+line option `-c safe.directory=<path>`.
 +
 The value of this setting is interpolated, i.e. `~/<path>` expands to a
 path relative to the home directory and `%(prefix)/<path>` expands to a

Documentation/config/sparse.txt

@@ -1,27 +0,0 @@
-sparse.expectFilesOutsideOfPatterns::
-	Typically with sparse checkouts, files not matching any
-	sparsity patterns are marked with a SKIP_WORKTREE bit in the
-	index and are missing from the working tree.  Accordingly, Git
-	will ordinarily check whether files with the SKIP_WORKTREE bit
-	are in fact present in the working tree contrary to
-	expectations.  If Git finds any, it marks those paths as
-	present by clearing the relevant SKIP_WORKTREE bits.  This
-	option can be used to tell Git that such
-	present-despite-skipped files are expected and to stop
-	checking for them.
-+
-The default is `false`, which allows Git to automatically recover
-from the list of files in the index and working tree falling out of
-sync.
-+
-Set this to `true` if you are in a setup where some external factor
-relieves Git of the responsibility for maintaining the consistency
-between the presence of working tree files and sparsity patterns.  For
-example, if you have a Git-aware virtual file system that has a robust
-mechanism for keeping the working tree and the sparsity patterns up to
-date based on access patterns.
-+
-Regardless of this setting, Git does not check for
-present-despite-skipped files unless sparse checkout is enabled, so
-this config option has no effect unless `core.sparseCheckout` is
-`true`.

Documentation/config/stash.txt

@@ -1,3 +1,10 @@
+stash.useBuiltin::
+	Unused configuration variable.  Used in Git versions 2.22 to
+	2.26 as an escape hatch to enable the legacy shellscript
+	implementation of stash.  Now the built-in rewrite of it in C
+	is always used. Setting this will emit a warning, to alert any
+	remaining users that setting this now does nothing.
+
 stash.showIncludeUntracked::
 	If this is set to true, the `git stash show` command will show
 	the untracked files of a stash entry.  Defaults to false. See

Documentation/config/submodule.txt

@@ -59,33 +59,18 @@ submodule.active::
 
 submodule.recurse::
 	A boolean indicating if commands should enable the `--recurse-submodules`
-	option by default. Defaults to false.
-+
-When set to true, it can be deactivated via the
-`--no-recurse-submodules` option. Note that some Git commands
-lacking this option may call some of the above commands affected by
-`submodule.recurse`; for instance `git remote update` will call
-`git fetch` but does not have a `--no-recurse-submodules` option.
-For these commands a workaround is to temporarily change the
-configuration value by using `git -c submodule.recurse=0`.
-+
-The following list shows the commands that accept
-`--recurse-submodules` and whether they are supported by this
-setting.
-
-* `checkout`, `fetch`, `grep`, `pull`, `push`, `read-tree`,
-`reset`, `restore` and `switch` are always supported.
-* `clone` and `ls-files` are not supported.
-* `branch` is supported only if `submodule.propagateBranches` is
-enabled
-
-submodule.propagateBranches::
-	[EXPERIMENTAL] A boolean that enables branching support when
-	using `--recurse-submodules` or `submodule.recurse=true`.
-	Enabling this will allow certain commands to accept
-	`--recurse-submodules` and certain commands that already accept
-	`--recurse-submodules` will now consider branches.
+	option by default.
+	Applies to all commands that support this option
+	(`checkout`, `fetch`, `grep`, `pull`, `push`, `read-tree`, `reset`,
+	`restore` and `switch`) except `clone` and `ls-files`.
 	Defaults to false.
+	When set to true, it can be deactivated via the
+	`--no-recurse-submodules` option. Note that some Git commands
+	lacking this option may call some of the above commands affected by
+	`submodule.recurse`; for instance `git remote update` will call
+	`git fetch` but does not have a `--no-recurse-submodules` option.
+	For these commands a workaround is to temporarily change the
+	configuration value by using `git -c submodule.recurse=0`.
 
 submodule.fetchJobs::
 	Specifies how many submodules are fetched/cloned at the same time.

Documentation/config/transfer.txt

@@ -1,41 +1,3 @@
-transfer.credentialsInUrl::
-	A configured URL can contain plaintext credentials in the form
-	`<protocol>://<user>:<password>@<domain>/<path>`. You may want
-	to warn or forbid the use of such configuration (in favor of
-	using linkgit:git-credential[1]). This will be used on
-	linkgit:git-clone[1], linkgit:git-fetch[1], linkgit:git-push[1],
-	and any other direct use of the configured URL.
-+
-Note that this is currently limited to detecting credentials in
-`remote.<name>.url` configuration, it won't detect credentials in
-`remote.<name>.pushurl` configuration.
-+
-You might want to enable this to prevent inadvertent credentials
-exposure, e.g. because:
-+
-* The OS or system where you're running git may not provide way way or
-  otherwise allow you to configure the permissions of the
-  configuration file where the username and/or password are stored.
-* Even if it does, having such data stored "at rest" might expose you
-  in other ways, e.g. a backup process might copy the data to another
-  system.
-* The git programs will pass the full URL to one another as arguments
-  on the command-line, meaning the credentials will be exposed to oher
-  users on OS's or systems that allow other users to see the full
-  process list of other users. On linux the "hidepid" setting
-  documented in procfs(5) allows for configuring this behavior.
-+
-If such concerns don't apply to you then you probably don't need to be
-concerned about credentials exposure due to storing that sensitive
-data in git's configuration files. If you do want to use this, set
-`transfer.credentialsInUrl` to one of these values:
-+
-* `allow` (default): Git will proceed with its activity without warning.
-* `warn`: Git will write a warning message to `stderr` when parsing a URL
-  with a plaintext credential.
-* `die`: Git will write a failure message to `stderr` when parsing a URL
-  with a plaintext credential.
-
 transfer.fsckObjects::
 	When `fetch.fsckObjects` or `receive.fsckObjects` are
 	not set, the value of this variable is used instead.

Documentation/config/user.txt

@@ -36,13 +36,3 @@ user.signingKey::
 	commit, you can override the default selection with this variable.
 	This option is passed unchanged to gpg's --local-user parameter,
 	so you may specify a key using any method that gpg supports.
-	If gpg.format is set to `ssh` this can contain the path to either
-	your private ssh key or the public key when ssh-agent is used.
-	Alternatively it can contain a public key prefixed with `key::`
-	directly (e.g.: "key::ssh-rsa XXXXXX identifier"). The private key
-	needs to be available via ssh-agent. If not set git will call
-	gpg.ssh.defaultKeyCommand (e.g.: "ssh-add -L") and try to use the
-	first key available. For backward compatibility, a raw key which
-	begins with "ssh-", such as "ssh-rsa XXXXXX identifier", is treated
-	as "key::ssh-rsa XXXXXX identifier", but this form is deprecated;
-	use the `key::` form instead.

Documentation/date-formats.txt

@@ -5,9 +5,9 @@ The `GIT_AUTHOR_DATE` and `GIT_COMMITTER_DATE` environment variables
 support the following date formats:
 
 Git internal format::
-	It is `<unix-timestamp> <time-zone-offset>`, where
-	`<unix-timestamp>` is the number of seconds since the UNIX epoch.
-	`<time-zone-offset>` is a positive or negative offset from UTC.
+	It is `<unix timestamp> <time zone offset>`, where `<unix
+	timestamp>` is the number of seconds since the UNIX epoch.
+	`<time zone offset>` is a positive or negative offset from UTC.
 	For example CET (which is 1 hour ahead of UTC) is `+0100`.
 
 RFC 2822::

Documentation/diff-format.txt

@@ -59,7 +59,7 @@ Possible status letters are:
 - D: deletion of a file
 - M: modification of the contents or mode of a file
 - R: renaming of a file
-- T: change in the type of the file (regular file, symbolic link or submodule)
+- T: change in the type of the file
 - U: file is unmerged (you must complete the merge before it can
   be committed)
 - X: "unknown" change type (most probably a bug, please report it)

Documentation/diff-options.txt

@@ -34,7 +34,7 @@ endif::git-diff[]
 endif::git-format-patch[]
 
 ifdef::git-log[]
---diff-merges=(off|none|on|first-parent|1|separate|m|combined|c|dense-combined|cc|remerge|r)::
+--diff-merges=(off|none|on|first-parent|1|separate|m|combined|c|dense-combined|cc)::
 --no-diff-merges::
 	Specify diff format to be used for merge commits. Default is
 	{diff-merges-default} unless `--first-parent` is in use, in which case
@@ -64,18 +64,6 @@ ifdef::git-log[]
 	each of the parents. Separate log entry and diff is generated
 	for each parent.
 +
---diff-merges=remerge:::
---diff-merges=r:::
---remerge-diff:::
-	With this option, two-parent merge commits are remerged to
-	create a temporary tree object -- potentially containing files
-	with conflict markers and such.  A diff is then shown between
-	that temporary tree and the actual merge commit.
-+
-The output emitted when this option is used is subject to change, and
-so is its interaction with other options (unless explicitly
-documented).
-+
 --diff-merges=combined:::
 --diff-merges=c:::
 -c:::
@@ -628,8 +616,11 @@ ifndef::git-format-patch[]
 Also, these upper-case letters can be downcased to exclude.  E.g.
 `--diff-filter=ad` excludes added and deleted paths.
 +
-Note that not all diffs can feature all types. For instance, copied and
-renamed entries cannot appear if detection for those types is disabled.
+Note that not all diffs can feature all types. For instance, diffs
+from the index to the working tree can never have Added entries
+(because the set of paths included in the diff is limited by what is in
+the index).  Similarly, copied and renamed entries cannot appear if
+detection for those types is disabled.
 
 -S<string>::
 	Look for differences that change the number of occurrences of

Documentation/fetch-options.txt

@@ -71,7 +71,6 @@ configuration variables documented in linkgit:git-config[1], and the
 	ancestors of the provided `--negotiation-tip=*` arguments,
 	which we have in common with the server.
 +
-This is incompatible with `--recurse-submodules=[yes|on-demand]`.
 Internally this is used to implement the `push.negotiate` option, see
 linkgit:git-config[1].
 
@@ -163,16 +162,6 @@ endif::git-pull[]
 	behavior for a remote may be specified with the remote.<name>.tagOpt
 	setting. See linkgit:git-config[1].
 
-ifndef::git-pull[]
---refetch::
-	Instead of negotiating with the server to avoid transferring commits and
-	associated objects that are already present locally, this option fetches
-	all objects as a fresh clone would. Use this to reapply a partial clone
-	filter from configuration or using `--filter=` when the filter
-	definition has changed. Automatic post-fetch maintenance will perform
-	object database pack consolidation to remove any duplicate objects.
-endif::git-pull[]
-
 --refmap=<refspec>::
 	When fetching refs listed on the command line, use the
 	specified refspec (can be given more than once) to map the
@@ -196,23 +185,15 @@ endif::git-pull[]
 ifndef::git-pull[]
 --recurse-submodules[=yes|on-demand|no]::
 	This option controls if and under what conditions new commits of
-	submodules should be fetched too. When recursing through submodules,
-	`git fetch` always attempts to fetch "changed" submodules, that is, a
-	submodule that has commits that are referenced by a newly fetched
-	superproject commit but are missing in the local submodule clone. A
-	changed submodule can be fetched as long as it is present locally e.g.
-	in `$GIT_DIR/modules/` (see linkgit:gitsubmodules[7]); if the upstream
-	adds a new submodule, that submodule cannot be fetched until it is
-	cloned e.g. by `git submodule update`.
-+
-When set to 'on-demand', only changed submodules are fetched. When set
-to 'yes', all populated submodules are fetched and submodules that are
-both unpopulated and changed are fetched. When set to 'no', submodules
-are never fetched.
-+
-When unspecified, this uses the value of `fetch.recurseSubmodules` if it
-is set (see linkgit:git-config[1]), defaulting to 'on-demand' if unset.
-When this option is used without any value, it defaults to 'yes'.
+	populated submodules should be fetched too. It can be used as a
+	boolean option to completely disable recursion when set to 'no' or to
+	unconditionally recurse into all populated submodules when set to
+	'yes', which is the default when this option is used without any
+	value. Use 'on-demand' to only recurse into a populated submodule
+	when the superproject retrieves a commit that updates the submodule's
+	reference to a commit that isn't already in the local submodule
+	clone. By default, 'on-demand' is used, unless
+	`fetch.recurseSubmodules` is set (see linkgit:git-config[1]).
 endif::git-pull[]
 
 -j::

Documentation/git-add.txt

@@ -9,7 +9,7 @@ SYNOPSIS
 --------
 [verse]
 'git add' [--verbose | -v] [--dry-run | -n] [--force | -f] [--interactive | -i] [--patch | -p]
-	  [--edit | -e] [--[no-]all | --[no-]ignore-removal | [--update | -u]] [--sparse]
+	  [--edit | -e] [--[no-]all | --[no-]ignore-removal | [--update | -u]]
 	  [--intent-to-add | -N] [--refresh] [--ignore-errors] [--ignore-missing] [--renormalize]
 	  [--chmod=(+|-)x] [--pathspec-from-file=<file> [--pathspec-file-nul]]
 	  [--] [<pathspec>...]
@@ -79,13 +79,6 @@ in linkgit:gitglossary[7].
 --force::
 	Allow adding otherwise ignored files.
 
---sparse::
-	Allow updating index entries outside of the sparse-checkout cone.
-	Normally, `git add` refuses to update index entries whose paths do
-	not fit within the sparse-checkout cone, since those files might
-	be removed from the working tree without warning. See
-	linkgit:git-sparse-checkout[1] for more details.
-
 -i::
 --interactive::
 	Add modified contents in the working tree interactively to

Documentation/git-am.txt

@@ -16,9 +16,8 @@ SYNOPSIS
 	 [--exclude=<path>] [--include=<path>] [--reject] [-q | --quiet]
 	 [--[no-]scissors] [-S[<keyid>]] [--patch-format=<format>]
 	 [--quoted-cr=<action>]
-	 [--empty=(stop|drop|keep)]
 	 [(<mbox> | <Maildir>)...]
-'git am' (--continue | --skip | --abort | --quit | --show-current-patch[=(diff|raw)] | --allow-empty)
+'git am' (--continue | --skip | --abort | --quit | --show-current-patch[=(diff|raw)])
 
 DESCRIPTION
 -----------
@@ -64,14 +63,6 @@ OPTIONS
 --quoted-cr=<action>::
 	This flag will be passed down to 'git mailinfo' (see linkgit:git-mailinfo[1]).
 
---empty=(stop|drop|keep)::
-	By default, or when the option is set to 'stop', the command
-	errors out on an input e-mail message lacking a patch
-	and stops into the middle of the current am session. When this
-	option is set to 'drop', skip such an e-mail message instead.
-	When this option is set to 'keep', create an empty commit,
-	recording the contents of the e-mail message as its log.
-
 -m::
 --message-id::
 	Pass the `-m` flag to 'git mailinfo' (see linkgit:git-mailinfo[1]),
@@ -200,11 +191,6 @@ default.   You can use `--no-utf8` to override this.
 	the e-mail message; if `diff`, show the diff portion only.
 	Defaults to `raw`.
 
---allow-empty::
-	After a patch failure on an input e-mail message lacking a patch,
-	create an empty commit with the contents of the e-mail message
-	as its log message.
-
 DISCUSSION
 ----------
 

Documentation/git-apply.txt

@@ -16,7 +16,7 @@ SYNOPSIS
 	  [--ignore-space-change | --ignore-whitespace]
 	  [--whitespace=(nowarn|warn|fix|error|error-all)]
 	  [--exclude=<path>] [--include=<path>] [--directory=<root>]
-	  [--verbose | --quiet] [--unsafe-paths] [--allow-empty] [<patch>...]
+	  [--verbose] [--unsafe-paths] [<patch>...]
 
 DESCRIPTION
 -----------
@@ -228,11 +228,6 @@ behavior:
 	current patch being applied will be printed. This option will cause
 	additional information to be reported.
 
--q::
---quiet::
-	Suppress stderr output. Messages about patch status and progress
-	will not be printed.
-
 --recount::
 	Do not trust the line counts in the hunk headers, but infer them
 	by inspecting the patch (e.g. after editing the patch without
@@ -256,10 +251,6 @@ When `git apply` is used as a "better GNU patch", the user can pass
 the `--unsafe-paths` option to override this safety check.  This option
 has no effect when `--index` or `--cached` is in use.
 
---allow-empty::
-	Don't return error for patches containing no diff. This includes
-	empty patches and patches with commit text only.
-
 CONFIGURATION
 -------------
 

Documentation/git-archimport.txt

@@ -9,14 +9,14 @@ git-archimport - Import a GNU Arch repository into Git
 SYNOPSIS
 --------
 [verse]
-'git archimport' [-h] [-v] [-o] [-a] [-f] [-T] [-D <depth>] [-t <tempdir>]
-	       <archive>/<branch>[:<git-branch>]...
+'git archimport' [-h] [-v] [-o] [-a] [-f] [-T] [-D depth] [-t tempdir]
+               <archive/branch>[:<git-branch>] ...
 
 DESCRIPTION
 -----------
 Imports a project from one or more GNU Arch repositories.
 It will follow branches
-and repositories within the namespaces defined by the <archive>/<branch>
+and repositories within the namespaces defined by the <archive/branch>
 parameters supplied. If it cannot find the remote branch a merge comes from
 it will just import it as a regular commit. If it can find it, it will mark it
 as a merge whenever possible (see discussion below).
@@ -27,7 +27,7 @@ import new branches within the provided roots.
 
 It expects to be dealing with one project only. If it sees
 branches that have different roots, it will refuse to run. In that case,
-edit your <archive>/<branch> parameters to define clearly the scope of the
+edit your <archive/branch> parameters to define clearly the scope of the
 import.
 
 'git archimport' uses `tla` extensively in the background to access the
@@ -42,7 +42,7 @@ incremental imports.
 
 While 'git archimport' will try to create sensible branch names for the
 archives that it imports, it is also possible to specify Git branch names
-manually.  To do so, write a Git branch name after each <archive>/<branch>
+manually.  To do so, write a Git branch name after each <archive/branch>
 parameter, separated by a colon.  This way, you can shorten the Arch
 branch names and convert Arch jargon to Git jargon, for example mapping a
 "PROJECT{litdd}devo{litdd}VERSION" branch to "master".
@@ -104,8 +104,8 @@ OPTIONS
 	Override the default tempdir.
 
 
-<archive>/<branch>::
-	<archive>/<branch> identifier in a format that `tla log` understands.
+<archive/branch>::
+	Archive/branch identifier in a format that `tla log` understands.
 
 
 GIT

Documentation/git-archive.txt

@@ -49,9 +49,7 @@ OPTIONS
 	Report progress to stderr.
 
 --prefix=<prefix>/::
-	Prepend <prefix>/ to paths in the archive.  Can be repeated; its
-	rightmost value is used for all tracked files.  See below which
-	value gets used by `--add-file` and `--add-virtual-file`.
+	Prepend <prefix>/ to each filename in the archive.
 
 -o <file>::
 --output=<file>::
@@ -59,26 +57,9 @@ OPTIONS
 
 --add-file=<file>::
 	Add a non-tracked file to the archive.  Can be repeated to add
-	multiple files.  The path of the file in the archive is built by
-	concatenating the value of the last `--prefix` option (if any)
-	before this `--add-file` and the basename of <file>.
-
---add-virtual-file=<path>:<content>::
-	Add the specified contents to the archive.  Can be repeated to add
 	multiple files.  The path of the file in the archive is built
-	by concatenating the value of the last `--prefix` option (if any)
-	before this `--add-virtual-file` and `<path>`.
-+
-The `<path>` argument can start and end with a literal double-quote
-character; the contained file name is interpreted as a C-style string,
-i.e. the backslash is interpreted as escape character. The path must
-be quoted if it contains a colon, to avoid the colon from being
-misinterpreted as the separator between the path and the contents, or
-if the path begins or ends with a double-quote character.
-+
-The file mode is limited to a regular file, and the option may be
-subject to platform-dependent command-line limits. For non-trivial
-cases, write an untracked file and use `--add-file` instead.
+	by concatenating the value for `--prefix` (if any) and the
+	basename of <file>.
 
 --worktree-attributes::
 	Look for attributes in .gitattributes files in the working tree
@@ -112,19 +93,12 @@ BACKEND EXTRA OPTIONS
 
 zip
 ~~~
--<digit>::
-	Specify compression level.  Larger values allow the command
-	to spend more time to compress to smaller size.  Supported
-	values are from `-0` (store-only) to `-9` (best ratio).
-	Default is `-6` if not given.
+-0::
+	Store the files instead of deflating them.
+-9::
+	Highest and slowest compression level.  You can specify any
+	number from 1 to 9 to adjust compression speed and ratio.
 
-tar
-~~~
--<number>::
-	Specify compression level. The value will be passed to the
-	compression command configured in `tar.<format>.command`. See
-	manual page of the configured command for the list of supported
-	levels and the default level if this option isn't specified.
 
 CONFIGURATION
 -------------
@@ -213,12 +187,6 @@ EXAMPLES
 	commit on the current branch. Note that the output format is
 	inferred by the extension of the output file.
 
-`git archive -o latest.tar --prefix=build/ --add-file=configure --prefix= HEAD`::
-
-	Creates a tar archive that contains the contents of the latest
-	commit on the current branch with no prefix and the untracked
-	file 'configure' with the prefix 'build/'.
-
 `git config tar.tar.xz.command "xz -c"`::
 
 	Configure a "tar.xz" format for making LZMA-compressed tarfiles.

Documentation/git-blame.txt

@@ -11,8 +11,8 @@ SYNOPSIS
 'git blame' [-c] [-b] [-l] [--root] [-t] [-f] [-n] [-s] [-e] [-p] [-w] [--incremental]
 	    [-L <range>] [-S <revs-file>] [-M] [-C] [-C] [-C] [--since=<date>]
 	    [--ignore-rev <rev>] [--ignore-revs-file <file>]
-	    [--color-lines] [--color-by-age] [--progress] [--abbrev=<n>]
-	    [<rev> | --contents <file> | --reverse <rev>..<rev>] [--] <file>
+	    [--progress] [--abbrev=<n>] [<rev> | --contents <file> | --reverse <rev>..<rev>]
+	    [--] <file>
 
 DESCRIPTION
 -----------
@@ -93,19 +93,6 @@ include::blame-options.txt[]
 	is used for a caret to mark the boundary commit.
 
 
-THE DEFAULT FORMAT
-------------------
-
-When neither `--porcelain` nor `--incremental` option is specified,
-`git blame` will output annotation for each line with:
-
-- abbreviated object name for the commit the line came from;
-- author ident (by default author name and date, unless `-s` or `-e`
-  is specified); and
-- line number
-
-before the line contents.
-
 THE PORCELAIN FORMAT
 --------------------
 

Documentation/git-branch.txt

@@ -16,8 +16,7 @@ SYNOPSIS
 	[--points-at <object>] [--format=<format>]
 	[(-r | --remotes) | (-a | --all)]
 	[--list] [<pattern>...]
-'git branch' [--track[=(direct|inherit)] | --no-track] [-f]
-	[--recurse-submodules] <branchname> [<start-point>]
+'git branch' [--track | --no-track] [-f] <branchname> [<start-point>]
 'git branch' (--set-upstream-to=<upstream> | -u <upstream>) [<branchname>]
 'git branch' --unset-upstream [<branchname>]
 'git branch' (-m | -M) [<oldbranch>] <newbranch>
@@ -126,14 +125,14 @@ OPTIONS
 
 -m::
 --move::
-	Move/rename a branch, together with its config and reflog.
+	Move/rename a branch and the corresponding reflog.
 
 -M::
 	Shortcut for `--move --force`.
 
 -c::
 --copy::
-	Copy a branch, together with its config and reflog.
+	Copy a branch and the corresponding reflog.
 
 -C::
 	Shortcut for `--copy --force`.
@@ -207,54 +206,24 @@ This option is only applicable in non-verbose mode.
 	Display the full sha1s in the output listing rather than abbreviating them.
 
 -t::
---track[=(direct|inherit)]::
+--track::
 	When creating a new branch, set up `branch.<name>.remote` and
-	`branch.<name>.merge` configuration entries to set "upstream" tracking
-	configuration for the new branch. This
+	`branch.<name>.merge` configuration entries to mark the
+	start-point branch as "upstream" from the new branch. This
 	configuration will tell git to show the relationship between the
 	two branches in `git status` and `git branch -v`. Furthermore,
 	it directs `git pull` without arguments to pull from the
 	upstream when the new branch is checked out.
 +
-The exact upstream branch is chosen depending on the optional argument:
-`-t`, `--track`, or `--track=direct` means to use the start-point branch
-itself as the upstream; `--track=inherit` means to copy the upstream
-configuration of the start-point branch.
-+
-The branch.autoSetupMerge configuration variable specifies how `git switch`,
-`git checkout` and `git branch` should behave when neither `--track` nor
-`--no-track` are specified:
-+
-The default option, `true`, behaves as though `--track=direct`
-were given whenever the start-point is a remote-tracking branch.
-`false` behaves as if `--no-track` were given. `always` behaves as though
-`--track=direct` were given. `inherit` behaves as though `--track=inherit`
-were given. `simple` behaves as though `--track=direct` were given only when
-the start-point is a remote-tracking branch and the new branch has the same
-name as the remote branch.
-+
-See linkgit:git-pull[1] and linkgit:git-config[1] for additional discussion on
-how the `branch.<name>.remote` and `branch.<name>.merge` options are used.
+This behavior is the default when the start point is a remote-tracking branch.
+Set the branch.autoSetupMerge configuration variable to `false` if you
+want `git switch`, `git checkout` and `git branch` to always behave as if `--no-track`
+were given. Set it to `always` if you want this behavior when the
+start-point is either a local or remote-tracking branch.
 
 --no-track::
 	Do not set up "upstream" configuration, even if the
-	branch.autoSetupMerge configuration variable is set.
-
---recurse-submodules::
-	THIS OPTION IS EXPERIMENTAL! Causes the current command to
-	recurse into submodules if `submodule.propagateBranches` is
-	enabled. See `submodule.propagateBranches` in
-	linkgit:git-config[1]. Currently, only branch creation is
-	supported.
-+
-When used in branch creation, a new branch <branchname> will be created
-in the superproject and all of the submodules in the superproject's
-<start-point>. In submodules, the branch will point to the submodule
-commit in the superproject's <start-point> but the branch's tracking
-information will be set up based on the submodule's branches and remotes
-e.g. `git branch --recurse-submodules topic origin/main` will create the
-submodule branch "topic" that points to the submodule commit in the
-superproject's "origin/main", but tracks the submodule's "origin/main".
+	branch.autoSetupMerge configuration variable is true.
 
 --set-upstream::
 	As this option had confusing syntax, it is no longer supported.

Documentation/git-bundle.txt

@@ -13,7 +13,7 @@ SYNOPSIS
 		    [--version=<version>] <file> <git-rev-list-args>
 'git bundle' verify [-q | --quiet] <file>
 'git bundle' list-heads <file> [<refname>...]
-'git bundle' unbundle [--progress] <file> [<refname>...]
+'git bundle' unbundle <file> [<refname>...]
 
 DESCRIPTION
 -----------
@@ -51,10 +51,10 @@ using the `--thin` option to linkgit:git-pack-objects[1], and
 unbundled using the `--fix-thin` option to linkgit:git-index-pack[1].
 
 There is no option to create a "thick pack" when using revision
-exclusions, and users should not be concerned about the difference. By
-using "thin packs", bundles created using exclusions are smaller in
+exclusions, users should not be concerned about the difference. By
+using "thin packs" bundles created using exclusions are smaller in
 size. That they're "thin" under the hood is merely noted here as a
-curiosity, and as a reference to other documentation.
+curiosity, and as a reference to other documentation
 
 See link:technical/bundle-format.html[the `bundle-format`
 documentation] for more details and the discussion of "thin pack" in
@@ -75,11 +75,8 @@ verify <file>::
 	cleanly to the current repository.  This includes checks on the
 	bundle format itself as well as checking that the prerequisite
 	commits exist and are fully linked in the current repository.
-	Then, 'git bundle' prints a list of missing commits, if any.
-	Finally, information about additional capabilities, such as "object
-	filter", is printed. See "Capabilities" in link:technical/bundle-format.html
-	for more information. The exit code is zero for success, but will
-	be nonzero if the bundle file is invalid.
+	'git bundle' prints a list of missing commits, if any, and exits
+	with a non-zero status.
 
 list-heads <file>::
 	Lists the references defined in the bundle.  If followed by a
@@ -147,7 +144,7 @@ unbundle <file>::
 SPECIFYING REFERENCES
 ---------------------
 
-Revisions must be accompanied by reference names to be packaged in a
+Revisions must accompanied by reference names to be packaged in a
 bundle.
 
 More than one reference may be packaged, and more than one set of prerequisite objects can

Documentation/git-cat-file.txt

@@ -9,14 +9,8 @@ git-cat-file - Provide content or type and size information for repository objec
 SYNOPSIS
 --------
 [verse]
-'git cat-file' <type> <object>
-'git cat-file' (-e | -p) <object>
-'git cat-file' (-t | -s) [--allow-unknown-type] <object>
-'git cat-file' (--batch | --batch-check | --batch-command) [--batch-all-objects]
-	     [--buffer] [--follow-symlinks] [--unordered]
-	     [--textconv | --filters]
-'git cat-file' (--textconv | --filters)
-	     [<rev>:<path|tree-ish> | --path=<path|tree-ish> <rev>]
+'git cat-file' (-t [--allow-unknown-type]| -s [--allow-unknown-type]| -e | -p | <type> | --textconv | --filters ) [--path=<path>] <object>
+'git cat-file' (--batch[=<format>] | --batch-check[=<format>]) [ --textconv | --filters ] [--follow-symlinks]
 
 DESCRIPTION
 -----------
@@ -96,48 +90,19 @@ OPTIONS
 	need to specify the path, separated by whitespace.  See the
 	section `BATCH OUTPUT` below for details.
 
---batch-command::
---batch-command=<format>::
-	Enter a command mode that reads commands and arguments from stdin. May
-	only be combined with `--buffer`, `--textconv` or `--filters`. In the
-	case of `--textconv` or `--filters`, the input lines also need to specify
-	the path, separated by whitespace. See the section `BATCH OUTPUT` below
-	for details.
-+
-`--batch-command` recognizes the following commands:
-+
---
-contents <object>::
-	Print object contents for object reference `<object>`. This corresponds to
-	the output of `--batch`.
-
-info <object>::
-	Print object info for object reference `<object>`. This corresponds to the
-	output of `--batch-check`.
-
-flush::
-	Used with `--buffer` to execute all preceding commands that were issued
-	since the beginning or since the last flush was issued. When `--buffer`
-	is used, no output will come until a `flush` is issued. When `--buffer`
-	is not used, commands are flushed each time without issuing `flush`.
---
-+
-
 --batch-all-objects::
 	Instead of reading a list of objects on stdin, perform the
 	requested batch operation on all objects in the repository and
 	any alternate object stores (not just reachable objects).
-	Requires `--batch` or `--batch-check` be specified. By default,
-	the objects are visited in order sorted by their hashes; see
-	also `--unordered` below. Objects are presented as-is, without
-	respecting the "replace" mechanism of linkgit:git-replace[1].
+	Requires `--batch` or `--batch-check` be specified. Note that
+	the objects are visited in order sorted by their hashes.
 
 --buffer::
 	Normally batch output is flushed after each object is output, so
 	that a process can interactively read and write from
 	`cat-file`. With this option, the output uses normal stdio
 	buffering; this is much more efficient when invoking
-	`--batch-check` or `--batch-command` on a large number of objects.
+	`--batch-check` on a large number of objects.
 
 --unordered::
 	When `--batch-all-objects` is in use, visit objects in an
@@ -229,13 +194,6 @@ from stdin, one per line, and print information about them. By default,
 the whole line is considered as an object, as if it were fed to
 linkgit:git-rev-parse[1].
 
-When `--batch-command` is given, `cat-file` will read commands from stdin,
-one per line, and print information based on the command given. With
-`--batch-command`, the `info` command followed by an object will print
-information about the object the same way `--batch-check` would, and the
-`contents` command followed by an object prints contents in the same way
-`--batch` would.
-
 You can specify the information shown for each object by using a custom
 `<format>`. The `<format>` is copied literally to stdout for each
 object, with placeholders of the form `%(atom)` expanded, followed by a
@@ -271,9 +229,9 @@ newline. The available atoms are:
 If no format is specified, the default format is `%(objectname)
 %(objecttype) %(objectsize)`.
 
-If `--batch` is specified, or if `--batch-command` is used with the `contents`
-command, the object information is followed by the object contents (consisting
-of `%(objectsize)` bytes), followed by a newline.
+If `--batch` is specified, the object information is followed by the
+object contents (consisting of `%(objectsize)` bytes), followed by a
+newline.
 
 For example, `--batch` without a custom format would produce:
 

Documentation/git-check-ignore.txt

@@ -33,7 +33,7 @@ OPTIONS
 	Instead of printing the paths that are excluded, for each path
 	that matches an exclude pattern, print the exclude pattern
 	together with the path.  (Matching an exclude pattern usually
-	means the path is excluded, but if the pattern begins with "`!`"
+	means the path is excluded, but if the pattern begins with '!'
 	then it is a negated pattern and matching it means the path is
 	NOT excluded.)
 +
@@ -77,7 +77,7 @@ If `--verbose` is specified, the output is a series of lines of the form:
 <pathname> is the path of a file being queried, <pattern> is the
 matching pattern, <source> is the pattern's source file, and <linenum>
 is the line number of the pattern within that source.  If the pattern
-contained a "`!`" prefix or "`/`" suffix, it will be preserved in the
+contained a `!` prefix or `/` suffix, it will be preserved in the
 output.  <source> will be an absolute path when referring to the file
 configured by `core.excludesFile`, or relative to the repository root
 when referring to `.git/info/exclude` or a per-directory exclude file.

Documentation/git-checkout-index.txt

@@ -12,7 +12,6 @@ SYNOPSIS
 'git checkout-index' [-u] [-q] [-a] [-f] [-n] [--prefix=<string>]
 		   [--stage=<number>|all]
 		   [--temp]
-		   [--ignore-skip-worktree-bits]
 		   [-z] [--stdin]
 		   [--] [<file>...]
 
@@ -38,9 +37,8 @@ OPTIONS
 
 -a::
 --all::
-	checks out all files in the index except for those with the
-	skip-worktree bit set (see `--ignore-skip-worktree-bits`).
-	Cannot be used together with explicit filenames.
+	checks out all files in the index.  Cannot be used
+	together with explicit filenames.
 
 -n::
 --no-create::
@@ -61,10 +59,6 @@ OPTIONS
 	write the content to temporary files.  The temporary name
 	associations will be written to stdout.
 
---ignore-skip-worktree-bits::
-	Check out all files, including those with the skip-worktree bit
-	set.
-
 --stdin::
 	Instead of taking list of paths from the command line,
 	read list of paths from the standard input.  Paths are

Documentation/git-checkout.txt

@@ -11,7 +11,7 @@ SYNOPSIS
 'git checkout' [-q] [-f] [-m] [<branch>]
 'git checkout' [-q] [-f] [-m] --detach [<branch>]
 'git checkout' [-q] [-f] [-m] [--detach] <commit>
-'git checkout' [-q] [-f] [-m] [[-b|-B|--orphan] <new-branch>] [<start-point>]
+'git checkout' [-q] [-f] [-m] [[-b|-B|--orphan] <new_branch>] [<start_point>]
 'git checkout' [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>...
 'git checkout' [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul]
 'git checkout' (-p|--patch) [<tree-ish>] [--] [<pathspec>...]
@@ -43,7 +43,7 @@ You could omit `<branch>`, in which case the command degenerates to
 rather expensive side-effects to show only the tracking information,
 if exists, for the current branch.
 
-'git checkout' -b|-B <new-branch> [<start-point>]::
+'git checkout' -b|-B <new_branch> [<start point>]::
 
 	Specifying `-b` causes a new branch to be created as if
 	linkgit:git-branch[1] were called and then checked out.  In
@@ -52,11 +52,11 @@ if exists, for the current branch.
 	`--track` without `-b` implies branch creation; see the
 	description of `--track` below.
 +
-If `-B` is given, `<new-branch>` is created if it doesn't exist; otherwise, it
+If `-B` is given, `<new_branch>` is created if it doesn't exist; otherwise, it
 is reset. This is the transactional equivalent of
 +
 ------------
-$ git branch -f <branch> [<start-point>]
+$ git branch -f <branch> [<start point>]
 $ git checkout <branch>
 ------------
 +
@@ -118,9 +118,8 @@ OPTIONS
 -f::
 --force::
 	When switching branches, proceed even if the index or the
-	working tree differs from `HEAD`, and even if there are untracked
-	files in the way.  This is used to throw away local changes and
-	any untracked files or directories that are in the way.
+	working tree differs from `HEAD`.  This is used to throw away
+	local changes.
 +
 When checking out paths from the index, do not fail upon unmerged
 entries; instead, unmerged entries are ignored.
@@ -145,18 +144,18 @@ as `ours` (i.e. "our shared canonical history"), while what you did
 on your side branch as `theirs` (i.e. "one contributor's work on top
 of it").
 
--b <new-branch>::
-	Create a new branch named `<new-branch>` and start it at
-	`<start-point>`; see linkgit:git-branch[1] for details.
+-b <new_branch>::
+	Create a new branch named `<new_branch>` and start it at
+	`<start_point>`; see linkgit:git-branch[1] for details.
 
--B <new-branch>::
-	Creates the branch `<new-branch>` and start it at `<start-point>`;
-	if it already exists, then reset it to `<start-point>`. This is
+-B <new_branch>::
+	Creates the branch `<new_branch>` and start it at `<start_point>`;
+	if it already exists, then reset it to `<start_point>`. This is
 	equivalent to running "git branch" with "-f"; see
 	linkgit:git-branch[1] for details.
 
 -t::
---track[=(direct|inherit)]::
+--track::
 	When creating a new branch, set up "upstream" configuration. See
 	"--track" in linkgit:git-branch[1] for details.
 +
@@ -210,16 +209,16 @@ variable.
 	`<commit>` is not a branch name.  See the "DETACHED HEAD" section
 	below for details.
 
---orphan <new-branch>::
-	Create a new 'orphan' branch, named `<new-branch>`, started from
-	`<start-point>` and switch to it.  The first commit made on this
+--orphan <new_branch>::
+	Create a new 'orphan' branch, named `<new_branch>`, started from
+	`<start_point>` and switch to it.  The first commit made on this
 	new branch will have no parents and it will be the root of a new
 	history totally disconnected from all the other branches and
 	commits.
 +
 The index and the working tree are adjusted as if you had previously run
-`git checkout <start-point>`.  This allows you to start a new history
-that records a set of paths similar to `<start-point>` by easily running
+`git checkout <start_point>`.  This allows you to start a new history
+that records a set of paths similar to `<start_point>` by easily running
 `git commit -a` to make the root commit.
 +
 This can be useful when you want to publish the tree from a commit
@@ -229,7 +228,7 @@ whose full history contains proprietary or otherwise encumbered bits of
 code.
 +
 If you want to start a disconnected history that records a set of paths
-that is totally different from the one of `<start-point>`, then you should
+that is totally different from the one of `<start_point>`, then you should
 clear the index and the working tree right after creating the orphan
 branch by running `git rm -rf .` from the top level of the working tree.
 Afterwards you will be ready to prepare your new files, repopulating the
@@ -266,7 +265,8 @@ When switching branches with `--merge`, staged changes may be lost.
 	The same as `--merge` option above, but changes the way the
 	conflicting hunks are presented, overriding the
 	`merge.conflictStyle` configuration variable.  Possible values are
-	"merge" (default), "diff3", and "zdiff3".
+	"merge" (default) and "diff3" (in addition to what is shown by
+	"merge" style, shows the original contents).
 
 -p::
 --patch::
@@ -340,10 +340,10 @@ As a special case, you may use `A...B` as a shortcut for the
 merge base of `A` and `B` if there is exactly one merge base. You can
 leave out at most one of `A` and `B`, in which case it defaults to `HEAD`.
 
-<new-branch>::
+<new_branch>::
 	Name for the new branch.
 
-<start-point>::
+<start_point>::
 	The name of a commit at which to start the new branch; see
 	linkgit:git-branch[1] for details. Defaults to `HEAD`.
 +

Documentation/git-cherry-pick.txt

@@ -8,7 +8,7 @@ git-cherry-pick - Apply the changes introduced by some existing commits
 SYNOPSIS
 --------
 [verse]
-'git cherry-pick' [--edit] [-n] [-m <parent-number>] [-s] [-x] [--ff]
+'git cherry-pick' [--edit] [-n] [-m parent-number] [-s] [-x] [--ff]
 		  [-S[<keyid>]] <commit>...
 'git cherry-pick' (--continue | --skip | --abort | --quit)
 
@@ -81,8 +81,8 @@ OPTIONS
 	described above, and `-r` was to disable it.  Now the
 	default is not to do `-x` so this option is a no-op.
 
--m <parent-number>::
---mainline <parent-number>::
+-m parent-number::
+--mainline parent-number::
 	Usually you cannot cherry-pick a merge because you do not know which
 	side of the merge should be considered the mainline.  This
 	option specifies the parent number (starting from 1) of

Documentation/git-clone.txt

@@ -9,14 +9,14 @@ git-clone - Clone a repository into a new directory
 SYNOPSIS
 --------
 [verse]
-'git clone' [--template=<template-directory>]
+'git clone' [--template=<template_directory>]
 	  [-l] [-s] [--no-hardlinks] [-q] [-n] [--bare] [--mirror]
 	  [-o <name>] [-b <name>] [-u <upload-pack>] [--reference <repository>]
-	  [--dissociate] [--separate-git-dir <git-dir>]
+	  [--dissociate] [--separate-git-dir <git dir>]
 	  [--depth <depth>] [--[no-]single-branch] [--no-tags]
 	  [--recurse-submodules[=<pathspec>]] [--[no-]shallow-submodules]
 	  [--[no-]remote-submodules] [--jobs <n>] [--sparse] [--[no-]reject-shallow]
-	  [--filter=<filter> [--also-filter-submodules]] [--] <repository>
+	  [--filter=<filter>] [--] <repository>
 	  [<directory>]
 
 DESCRIPTION
@@ -167,10 +167,10 @@ objects from the source repository into a pack in the cloned repository.
 	configuration variables are created.
 
 --sparse::
-	Employ a sparse-checkout, with only files in the toplevel
-	directory initially being present.  The
-	linkgit:git-sparse-checkout[1] command can be used to grow the
-	working directory as needed.
+	Initialize the sparse-checkout file so the working
+	directory starts with only the files in the root
+	of the repository. The sparse-checkout file can be
+	modified to grow the working directory as needed.
 
 --filter=<filter-spec>::
 	Use the partial clone feature and request that the server sends
@@ -182,11 +182,6 @@ objects from the source repository into a pack in the cloned repository.
 	at least `<size>`. For more details on filter specifications, see
 	the `--filter` option in linkgit:git-rev-list[1].
 
---also-filter-submodules::
-	Also apply the partial clone filter to any submodules in the repository.
-	Requires `--filter` and `--recurse-submodules`. This can be turned on by
-	default by setting the `clone.filterSubmodules` config option.
-
 --mirror::
 	Set up a mirror of the source repository.  This implies `--bare`.
 	Compared to `--bare`, `--mirror` not only maps local branches of the
@@ -216,7 +211,7 @@ objects from the source repository into a pack in the cloned repository.
 	via ssh, this specifies a non-default path for the command
 	run on the other end.
 
---template=<template-directory>::
+--template=<template_directory>::
 	Specify the directory from which templates will be used;
 	(See the "TEMPLATE DIRECTORY" section of linkgit:git-init[1].)
 
@@ -299,7 +294,7 @@ or `--mirror` is given)
 	superproject's recorded SHA-1. Equivalent to passing `--remote` to
 	`git submodule update`.
 
---separate-git-dir=<git-dir>::
+--separate-git-dir=<git dir>::
 	Instead of placing the cloned repository where it is supposed
 	to be, place the cloned repository at the specified directory,
 	then make a filesystem-agnostic Git symbolic link to there.

Documentation/git-commit.txt

@@ -212,9 +212,8 @@ include::signoff-option.txt[]
 	each trailer would appear, and other details.
 
 -n::
---[no-]verify::
-	By default, the pre-commit and commit-msg hooks are run.
-	When any of `--no-verify` or `-n` is given, these are bypassed.
+--no-verify::
+	This option bypasses the pre-commit and commit-msg hooks.
 	See also linkgit:githooks[5].
 
 --allow-empty::

Documentation/git-config.txt

@@ -9,20 +9,20 @@ git-config - Get and set repository or global options
 SYNOPSIS
 --------
 [verse]
-'git config' [<file-option>] [--type=<type>] [--fixed-value] [--show-origin] [--show-scope] [-z|--null] <name> [<value> [<value-pattern>]]
-'git config' [<file-option>] [--type=<type>] --add <name> <value>
-'git config' [<file-option>] [--type=<type>] [--fixed-value] --replace-all <name> <value> [<value-pattern>]
-'git config' [<file-option>] [--type=<type>] [--show-origin] [--show-scope] [-z|--null] [--fixed-value] --get <name> [<value-pattern>]
-'git config' [<file-option>] [--type=<type>] [--show-origin] [--show-scope] [-z|--null] [--fixed-value] --get-all <name> [<value-pattern>]
-'git config' [<file-option>] [--type=<type>] [--show-origin] [--show-scope] [-z|--null] [--fixed-value] [--name-only] --get-regexp <name-regex> [<value-pattern>]
-'git config' [<file-option>] [--type=<type>] [-z|--null] --get-urlmatch <name> <URL>
-'git config' [<file-option>] [--fixed-value] --unset <name> [<value-pattern>]
-'git config' [<file-option>] [--fixed-value] --unset-all <name> [<value-pattern>]
-'git config' [<file-option>] --rename-section <old-name> <new-name>
-'git config' [<file-option>] --remove-section <name>
+'git config' [<file-option>] [--type=<type>] [--fixed-value] [--show-origin] [--show-scope] [-z|--null] name [value [value-pattern]]
+'git config' [<file-option>] [--type=<type>] --add name value
+'git config' [<file-option>] [--type=<type>] [--fixed-value] --replace-all name value [value-pattern]
+'git config' [<file-option>] [--type=<type>] [--show-origin] [--show-scope] [-z|--null] [--fixed-value] --get name [value-pattern]
+'git config' [<file-option>] [--type=<type>] [--show-origin] [--show-scope] [-z|--null] [--fixed-value] --get-all name [value-pattern]
+'git config' [<file-option>] [--type=<type>] [--show-origin] [--show-scope] [-z|--null] [--fixed-value] [--name-only] --get-regexp name_regex [value-pattern]
+'git config' [<file-option>] [--type=<type>] [-z|--null] --get-urlmatch name URL
+'git config' [<file-option>] [--fixed-value] --unset name [value-pattern]
+'git config' [<file-option>] [--fixed-value] --unset-all name [value-pattern]
+'git config' [<file-option>] --rename-section old_name new_name
+'git config' [<file-option>] --remove-section name
 'git config' [<file-option>] [--show-origin] [--show-scope] [-z|--null] [--name-only] -l | --list
-'git config' [<file-option>] --get-color <name> [<default>]
-'git config' [<file-option>] --get-colorbool <name> [<stdout-is-tty>]
+'git config' [<file-option>] --get-color name [default]
+'git config' [<file-option>] --get-colorbool name [stdout-is-tty]
 'git config' [<file-option>] -e | --edit
 
 DESCRIPTION
@@ -102,9 +102,9 @@ OPTIONS
 	in which section and variable names are lowercased, but subsection
 	names are not.
 
---get-urlmatch <name> <URL>::
+--get-urlmatch name URL::
 	When given a two-part name section.key, the value for
-	section.<URL>.key whose <URL> part matches the best to the
+	section.<url>.key whose <url> part matches the best to the
 	given URL is returned (if no such key exists, the value for
 	section.key is used as a fallback).  When given just the
 	section as name, do so for all the keys in the section and
@@ -141,16 +141,12 @@ from all available files.
 See also <<FILES>>.
 
 --worktree::
-	Similar to `--local` except that `$GIT_DIR/config.worktree` is
+	Similar to `--local` except that `.git/config.worktree` is
 	read from or written to if `extensions.worktreeConfig` is
-	enabled. If not it's the same as `--local`. Note that `$GIT_DIR`
-	is equal to `$GIT_COMMON_DIR` for the main working tree, but is of
-	the form `$GIT_DIR/worktrees/<id>/` for other working trees. See
-	linkgit:git-worktree[1] to learn how to enable
-	`extensions.worktreeConfig`.
+	present. If not it's the same as `--local`.
 
--f <config-file>::
---file <config-file>::
+-f config-file::
+--file config-file::
 	For writing options: write to the specified file rather than the
 	repository `.git/config`.
 +
@@ -159,7 +155,7 @@ available files.
 +
 See also <<FILES>>.
 
---blob <blob>::
+--blob blob::
 	Similar to `--file` but use the given blob instead of a file. E.g.
 	you can use 'master:.gitmodules' to read values from the file
 	'.gitmodules' in the master branch. See "SPECIFYING REVISIONS"
@@ -248,20 +244,20 @@ Valid `<type>`'s include:
 --show-scope::
 	Similar to `--show-origin` in that it augments the output of
 	all queried config options with the scope of that value
-	(worktree, local, global, system, command).
+	(local, global, system, command).
 
---get-colorbool <name> [<stdout-is-tty>]::
+--get-colorbool name [stdout-is-tty]::
 
-	Find the color setting for `<name>` (e.g. `color.diff`) and output
-	"true" or "false".  `<stdout-is-tty>` should be either "true" or
+	Find the color setting for `name` (e.g. `color.diff`) and output
+	"true" or "false".  `stdout-is-tty` should be either "true" or
 	"false", and is taken into account when configuration says
-	"auto".  If `<stdout-is-tty>` is missing, then checks the standard
+	"auto".  If `stdout-is-tty` is missing, then checks the standard
 	output of the command itself, and exits with status 0 if color
 	is to be used, or exits with status 1 otherwise.
 	When the color setting for `name` is undefined, the command uses
 	`color.ui` as fallback.
 
---get-color <name> [<default>]::
+--get-color name [default]::
 
 	Find the color configured for `name` (e.g. `color.diff.new`) and
 	output it as the ANSI color escape sequence to the standard

Documentation/git-credential-cache--daemon.txt

@@ -1,5 +1,5 @@
-git-credential-cache{litdd}daemon(1)
-====================================
+git-credential-cache--daemon(1)
+===============================
 
 NAME
 ----
@@ -8,7 +8,7 @@ git-credential-cache--daemon - Temporarily store user credentials in memory
 SYNOPSIS
 --------
 [verse]
-'git credential-cache{litdd}daemon' [--debug] <socket>
+git credential-cache--daemon [--debug] <socket>
 
 DESCRIPTION
 -----------

Documentation/git-credential.txt

@@ -8,7 +8,7 @@ git-credential - Retrieve and store user credentials
 SYNOPSIS
 --------
 ------------------
-'git credential' (fill|approve|reject)
+git credential <fill|approve|reject>
 ------------------
 
 DESCRIPTION

Documentation/git-cvsexportcommit.txt

@@ -9,8 +9,8 @@ git-cvsexportcommit - Export a single commit to a CVS checkout
 SYNOPSIS
 --------
 [verse]
-'git cvsexportcommit' [-h] [-u] [-v] [-c] [-P] [-p] [-a] [-d <cvsroot>]
-	[-w <cvs-workdir>] [-W] [-f] [-m <msgprefix>] [<parent-commit>] <commit-id>
+'git cvsexportcommit' [-h] [-u] [-v] [-c] [-P] [-p] [-a] [-d cvsroot]
+	[-w cvsworkdir] [-W] [-f] [-m msgprefix] [PARENTCOMMIT] COMMITID
 
 
 DESCRIPTION

Documentation/git-cvsimport.txt

@@ -11,9 +11,9 @@ SYNOPSIS
 [verse]
 'git cvsimport' [-o <branch-for-HEAD>] [-h] [-v] [-d <CVSROOT>]
 	      [-A <author-conv-file>] [-p <options-for-cvsps>] [-P <file>]
-	      [-C <git-repository>] [-z <fuzz>] [-i] [-k] [-u] [-s <subst>]
-	      [-a] [-m] [-M <regex>] [-S <regex>] [-L <commit-limit>]
-	      [-r <remote>] [-R] [<CVS-module>]
+	      [-C <git_repository>] [-z <fuzz>] [-i] [-k] [-u] [-s <subst>]
+	      [-a] [-m] [-M <regex>] [-S <regex>] [-L <commitlimit>]
+	      [-r <remote>] [-R] [<CVS_module>]
 
 
 DESCRIPTION
@@ -59,7 +59,7 @@ OPTIONS
 	from `CVS/Root`. If no such file exists, it checks for the
 	`CVSROOT` environment variable.
 
-<CVS-module>::
+<CVS_module>::
 	The CVS module you want to import. Relative to <CVSROOT>.
 	If not given, 'git cvsimport' tries to read it from
 	`CVS/Repository`.

Documentation/git-diff-files.txt

@@ -9,7 +9,7 @@ git-diff-files - Compares files in the working tree and the index
 SYNOPSIS
 --------
 [verse]
-'git diff-files' [-q] [-0|-1|-2|-3|-c|--cc] [<common-diff-options>] [<path>...]
+'git diff-files' [-q] [-0|-1|-2|-3|-c|--cc] [<common diff options>] [<path>...]
 
 DESCRIPTION
 -----------

Documentation/git-diff-index.txt

@@ -9,7 +9,7 @@ git-diff-index - Compare a tree to the working tree or index
 SYNOPSIS
 --------
 [verse]
-'git diff-index' [-m] [--cached] [--merge-base] [<common-diff-options>] <tree-ish> [<path>...]
+'git diff-index' [-m] [--cached] [--merge-base] [<common diff options>] <tree-ish> [<path>...]
 
 DESCRIPTION
 -----------

Documentation/git-diff-tree.txt

@@ -11,7 +11,7 @@ SYNOPSIS
 [verse]
 'git diff-tree' [--stdin] [-m] [-s] [-v] [--no-commit-id] [--pretty]
 	      [-t] [-r] [-c | --cc] [--combined-all-paths] [--root] [--merge-base]
-	      [<common-diff-options>] <tree-ish> [<tree-ish>] [<path>...]
+	      [<common diff options>] <tree-ish> [<tree-ish>] [<path>...]
 
 DESCRIPTION
 -----------

Documentation/git-fetch-pack.txt

@@ -101,10 +101,6 @@ be in a separate packet, and the list must end with a flush packet.
 	current shallow boundary instead of from the tip of each
 	remote branch history.
 
---refetch::
-	Skips negotiating commits with the server in order to fetch all matching
-	objects. Use to reapply a new partial clone blob/tree filter.
-
 --no-progress::
 	Do not show the progress.
 

Documentation/git-fetch.txt

@@ -287,10 +287,12 @@ include::transfer-data-leaks.txt[]
 
 BUGS
 ----
-Using --recurse-submodules can only fetch new commits in submodules that are
-present locally e.g. in `$GIT_DIR/modules/`. If the upstream adds a new
-submodule, that submodule cannot be fetched until it is cloned e.g. by `git
-submodule update`. This is expected to be fixed in a future Git version.
+Using --recurse-submodules can only fetch new commits in already checked
+out submodules right now. When e.g. upstream added a new submodule in the
+just fetched commits of the superproject the submodule itself cannot be
+fetched, making it impossible to check out that submodule later without
+having to do a fetch again. This is expected to be fixed in a future Git
+version.
 
 SEE ALSO
 --------

Documentation/git-fmt-merge-msg.txt

@@ -9,7 +9,7 @@ git-fmt-merge-msg - Produce a merge commit message
 SYNOPSIS
 --------
 [verse]
-'git fmt-merge-msg' [-m <message>] [--into-name <branch>] [--log[=<n>] | --no-log]
+'git fmt-merge-msg' [-m <message>] [--log[=<n>] | --no-log]
 'git fmt-merge-msg' [-m <message>] [--log[=<n>] | --no-log] -F <file>
 
 DESCRIPTION
@@ -44,10 +44,6 @@ OPTIONS
 	Use <message> instead of the branch names for the first line
 	of the log message.  For use with `--log`.
 
---into-name <branch>::
-	Prepare the merge message as if merging to the branch `<branch>`,
-	instead of the name of the real branch to which the merge is made.
-
 -F <file>::
 --file <file>::
 	Take the list of merged objects from <file> instead of

Documentation/git-for-each-ref.txt

@@ -235,15 +235,6 @@ and `date` to extract the named component.  For email fields (`authoremail`,
 without angle brackets, and `:localpart` to get the part before the `@` symbol
 out of the trimmed email.
 
-The raw data in an object is `raw`.
-
-raw:size::
-	The raw data size of the object.
-
-Note that `--format=%(raw)` can not be used with `--python`, `--shell`, `--tcl`,
-because such language may not support arbitrary binary data in their string
-variable type.
-
 The message in a commit or a tag object is `contents`, from which
 `contents:<part>` can be used to extract various parts out of:
 

Documentation/git-format-patch.txt

@@ -18,7 +18,7 @@ SYNOPSIS
 		   [-n | --numbered | -N | --no-numbered]
 		   [--start-number <n>] [--numbered-files]
 		   [--in-reply-to=<message id>] [--suffix=.<sfx>]
-		   [--ignore-if-in-upstream] [--always]
+		   [--ignore-if-in-upstream]
 		   [--cover-from-description=<mode>]
 		   [--rfc] [--subject-prefix=<subject prefix>]
 		   [(--reroll-count|-v) <n>]
@@ -192,10 +192,6 @@ will want to ensure that threading is disabled for `git send-email`.
 	patches being generated, and any patch that matches is
 	ignored.
 
---always::
-	Include patches for commits that do not introduce any change,
-	which are omitted by default.
-
 --cover-from-description=<mode>::
 	Controls which parts of the cover letter will be automatically
 	populated using the branch's description.
@@ -693,10 +689,10 @@ You can also use `git format-patch --base=P -3 C` to generate patches
 for A, B and C, and the identifiers for P, X, Y, Z are appended at the
 end of the first message.
 
-If set `--base=auto` in cmdline, it will automatically compute
-the base commit as the merge base of tip commit of the remote-tracking
+If set `--base=auto` in cmdline, it will track base commit automatically,
+the base commit will be the merge base of tip commit of the remote-tracking
 branch and revision-range specified in cmdline.
-For a local branch, you need to make it to track a remote branch by `git branch
+For a local branch, you need to track a remote branch by `git branch
 --set-upstream-to` before using this option.
 
 EXAMPLES

Documentation/git-fsck.txt

@@ -12,7 +12,7 @@ SYNOPSIS
 'git fsck' [--tags] [--root] [--unreachable] [--cache] [--no-reflogs]
 	 [--[no-]full] [--strict] [--verbose] [--lost-found]
 	 [--[no-]dangling] [--[no-]progress] [--connectivity-only]
-	 [--[no-]name-objects] [<object>...]
+	 [--[no-]name-objects] [<object>*]
 
 DESCRIPTION
 -----------

Documentation/git-fsmonitor--daemon.txt

@@ -1,75 +0,0 @@
-git-fsmonitor{litdd}daemon(1)
-=============================
-
-NAME
-----
-git-fsmonitor--daemon - A Built-in File System Monitor
-
-SYNOPSIS
---------
-[verse]
-'git fsmonitor{litdd}daemon' start
-'git fsmonitor{litdd}daemon' run
-'git fsmonitor{litdd}daemon' stop
-'git fsmonitor{litdd}daemon' status
-
-DESCRIPTION
------------
-
-A daemon to watch the working directory for file and directory
-changes using platform-specific file system notification facilities.
-
-This daemon communicates directly with commands like `git status`
-using the link:technical/api-simple-ipc.html[simple IPC] interface
-instead of the slower linkgit:githooks[5] interface.
-
-This daemon is built into Git so that no third-party tools are
-required.
-
-OPTIONS
--------
-
-start::
-	Starts a daemon in the background.
-
-run::
-	Runs a daemon in the foreground.
-
-stop::
-	Stops the daemon running in the current working
-	directory, if present.
-
-status::
-	Exits with zero status if a daemon is watching the
-	current working directory.
-
-REMARKS
--------
-
-This daemon is a long running process used to watch a single working
-directory and maintain a list of the recently changed files and
-directories.  Performance of commands such as `git status` can be
-increased if they just ask for a summary of changes to the working
-directory and can avoid scanning the disk.
-
-When `core.fsmonitor` is set to `true` (see linkgit:git-config[1])
-commands, such as `git status`, will ask the daemon for changes and
-automatically start it (if necessary).
-
-For more information see the "File System Monitor" section in
-linkgit:git-update-index[1].
-
-CAVEATS
--------
-
-The fsmonitor daemon does not currently know about submodules and does
-not know to filter out file system events that happen within a
-submodule.  If fsmonitor daemon is watching a super repo and a file is
-modified within the working directory of a submodule, it will report
-the change (as happening against the super repo).  However, the client
-will properly ignore these extra events, so performance may be affected
-but it will not cause an incorrect result.
-
-GIT
----
-Part of the linkgit:git[1] suite