Autogenerated HTML docs for v2.47.1-397-g23692e

Author: gitster

DecisionMaking.html

@@ -442,7 +442,7 @@
 <div id="header">
 <h1>Decision-Making Process in the Git Project</h1>
 <div class="details">
-<span id="revdate">2024-11-27</span>
+<span id="revdate">2024-12-04</span>
 </div>
 </div>
 <div id="content">

MyFirstContribution.html

@@ -442,7 +442,7 @@
 <div id="header">
 <h1>My First Contribution to the Git Project</h1>
 <div class="details">
-<span id="revdate">2024-11-27</span>
+<span id="revdate">2024-12-04</span>
 </div>
 </div>
 <div id="content">

MyFirstObjectWalk.html

@@ -442,7 +442,7 @@
 <div id="header">
 <h1>My First Object Walk</h1>
 <div class="details">
-<span id="revdate">2024-11-27</span>
+<span id="revdate">2024-12-04</span>
 </div>
 </div>
 <div id="content">

RelNotes/2.48.0.txt

@@ -19,12 +19,13 @@ UI, Workflows & Features
  * Documentation for "git bundle" saw improvements to more prominently
    call out the use of '--all' when creating bundles.
 
+ * Drop support for older libcURL and Perl.
+
 
 Performance, Internal Implementation, Development Support etc.
 --------------------------------------------------------------
 
  * Document "amlog" notes.
-   (merge ddfb5bcfc6 tb/notes-amlog-doc later to maint).
 
  * The way AsciiDoc is used for SYNOPSIS part of the manual pages has
    been revamped.  The sources, at least for the simple cases, got
@@ -94,13 +95,24 @@ Performance, Internal Implementation, Development Support etc.
  * We now ensure "index-pack" is used with the "--promisor" option
    only during a "git fetch".
 
+ * The migration procedure between two ref backends has been optimized.
+
+ * "git fsck" learned to issue warnings on "curiously formatted" ref
+   contents that have always been taken valid but something Git
+   wouldn't have written itself (e.g., missing terminating end-of-line
+   after the full object name).
+
+ * Work around Coverity warning that would not trigger in practice.
+
+ * Built-in Git subcommands are supplied the repository object to work
+   with; they learned to do the same when they invoke sub-subcommands.
+
 
 Fixes since v2.47
 -----------------
 
  * Doc update to clarify how periodical maintenance are scheduled,
    spread across time to avoid thundering hurds.
-   (merge 3d6ab4177d sk/doc-maintenance-schedule later to maint).
 
  * Use after free and double freeing at the end in "git log -L... -p"
    had been identified and fixed.
@@ -179,17 +191,15 @@ Fixes since v2.47
    been corrected.
    (merge b886db48c6 kn/ref-transaction-hook-with-reflog later to maint).
 
+ * Give a bit of advice/hint message when "git maintenance" stops finding a
+   lock file left by another instance that still is potentially running.
+   (merge ba874d1dac ps/gc-stale-lock-warning later to maint).
+
+ * Use the right helper program to measure file size in performance tests.
+   (merge 3f97f1bce6 tb/use-test-file-size-more later to maint).
+
  * Other code cleanup, docfix, build fix, etc.
-   (merge 1164e270b5 jk/output-prefix-cleanup later to maint).
-   (merge f36b8cbaef jh/config-unset-doc-fix later to maint).
-   (merge 4154ed4108 js/doc-platform-support-link-fix later to maint).
    (merge 77af53f56f aa/t7300-modernize later to maint).
-   (merge 8ead1bba3e jc/doc-refspec-syntax later to maint).
-   (merge 432f666aa6 kn/loose-object-layer-wo-global-hash later to maint).
-   (merge c4b8fb6ef2 kh/merge-tree-doc later to maint).
-   (merge b8139c8f4e kh/checkout-ignore-other-docfix later to maint).
-   (merge 6dab49b9fb tc/bundle-uri-leakfix later to maint).
-   (merge f1ed39987b xx/protocol-v2-doc-markup-fix later to maint).
-   (merge 41869f7447 ak/typofixes later to maint).
    (merge dcd590a39d bf/t-readme-mention-reftable later to maint).
    (merge 68e3c69efa kh/trailer-in-glossary later to maint).
+   (merge 91f88f76e6 tb/boundary-traversal-fix later to maint).

ReviewingGuidelines.html

@@ -442,7 +442,7 @@
 <div id="header">
 <h1>Reviewing Patches in the Git Project</h1>
 <div class="details">
-<span id="revdate">2024-11-27</span>
+<span id="revdate">2024-12-04</span>
 </div>
 </div>
 <div id="content">

SubmittingPatches.html

@@ -442,7 +442,7 @@
 <div id="header">
 <h1>Submitting Patches</h1>
 <div class="details">
-<span id="revdate">2024-11-27</span>
+<span id="revdate">2024-12-04</span>
 </div>
 </div>
 <div id="content">

ToolsForGit.html

@@ -442,7 +442,7 @@
 <div id="header">
 <h1>Tools for developing Git</h1>
 <div class="details">
-<span id="revdate">2024-11-27</span>
+<span id="revdate">2024-12-04</span>
 </div>
 </div>
 <div id="content">

diff-format.txt

@@ -1,25 +1,25 @@
 Raw output format
 -----------------
 
-The raw output format from "git-diff-index", "git-diff-tree",
-"git-diff-files" and "git diff --raw" are very similar.
+The raw output format from `git-diff-index`, `git-diff-tree`,
+`git-diff-files` and `git diff --raw` are very similar.
 
 These commands all compare two sets of things; what is
 compared differs:
 
-git-diff-index <tree-ish>::
-        compares the <tree-ish> and the files on the filesystem.
+`git-diff-index <tree-ish>`::
+	compares the _<tree-ish>_ and the files on the filesystem.
 
-git-diff-index --cached <tree-ish>::
-        compares the <tree-ish> and the index.
+`git-diff-index --cached <tree-ish>`::
+	compares the _<tree-ish>_ and the index.
 
-git-diff-tree [-r] <tree-ish-1> <tree-ish-2> [<pattern>...]::
+`git-diff-tree [-r] <tree-ish-1> <tree-ish-2> [<pattern>...]`::
         compares the trees named by the two arguments.
 
-git-diff-files [<pattern>...]::
+`git-diff-files [<pattern>...]`::
         compares the index and the files on the filesystem.
 
-The "git-diff-tree" command begins its output by printing the hash of
+The `git-diff-tree` command begins its output by printing the hash of
 what is being compared. After that, all the commands print one output
 line per changed file.
 
@@ -54,19 +54,19 @@ That is, from the left to the right:
 
 Possible status letters are:
 
-- A: addition of a file
-- C: copy of a file into a new one
-- 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)
-- U: file is unmerged (you must complete the merge before it can
+- `A`: addition of a file
+- `C`: copy of a file into a new one
+- `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)
+- `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)
+- `X`: "unknown" change type (most probably a bug, please report it)
 
-Status letters C and R are always followed by a score (denoting the
+Status letters `C` and `R` are always followed by a score (denoting the
 percentage of similarity between the source and target of the move or
-copy).  Status letter M may be followed by a score (denoting the
+copy).  Status letter `M` may be followed by a score (denoting the
 percentage of dissimilarity) for file rewrites.
 
 The sha1 for "dst" is shown as all 0's if a file on the filesystem
@@ -86,7 +86,7 @@ verbatim and the line is terminated by a NUL byte.
 diff format for merges
 ----------------------
 
-"git-diff-tree", "git-diff-files" and "git-diff --raw"
+`git-diff-tree`, `git-diff-files` and `git-diff --raw`
 can take `-c` or `--cc` option
 to generate diff output also for merge commits.  The output differs
 from the format described above in the following way:
@@ -128,7 +128,7 @@ other diff formats
 ------------------
 
 The `--summary` option describes newly added, deleted, renamed and
-copied files.  The `--stat` option adds diffstat(1) graph to the
+copied files.  The `--stat` option adds `diffstat`(1) graph to the
 output.  These options can be combined with other options, such as
 `-p`, and are meant for human consumption.
 

diff-generate-patch.txt

@@ -14,7 +14,7 @@ You can customize the creation of patch text via the
 `GIT_EXTERNAL_DIFF` and the `GIT_DIFF_OPTS` environment variables
 (see linkgit:git[1]), and the `diff` attribute (see linkgit:gitattributes[5]).
 
-What the -p option produces is slightly different from the traditional
+What the `-p` option produces is slightly different from the traditional
 diff format:
 
 1.   It is preceded by a "git diff" header that looks like this:
@@ -30,20 +30,21 @@ name of the source file of the rename/copy and the name of
 the file that the rename/copy produces, respectively.
 
 2.   It is followed by one or more extended header lines:
-
-       old mode <mode>
-       new mode <mode>
-       deleted file mode <mode>
-       new file mode <mode>
-       copy from <path>
-       copy to <path>
-       rename from <path>
-       rename to <path>
-       similarity index <number>
-       dissimilarity index <number>
-       index <hash>..<hash> <mode>
 +
-File modes are printed as 6-digit octal numbers including the file type
+[synopsis]
+old mode <mode>
+new mode <mode>
+deleted file mode <mode>
+new file mode <mode>
+copy from <path>
+copy to <path>
+rename from <path>
+rename to <path>
+similarity index <number>
+dissimilarity index <number>
+index <hash>..<hash> <mode>
++
+File modes _<mode>_ are printed as 6-digit octal numbers including the file type
 and file permission bits.
 +
 Path names in extended headers do not include the `a/` and `b/` prefixes.
@@ -56,7 +57,7 @@ files, while 100% dissimilarity means that no line from the old
 file made it into the new one.
 +
 The index line includes the blob object names before and after the change.
-The <mode> is included if the file mode does not change; otherwise,
+The _<mode>_ is included if the file mode does not change; otherwise,
 separate lines indicate the old and the new mode.
 
 3.  Pathnames with "unusual" characters are quoted as explained for
@@ -134,17 +135,18 @@ or like this (when the `--cc` option is used):
 
 2.   It is followed by one or more extended header lines
      (this example shows a merge with two parents):
-
-       index <hash>,<hash>..<hash>
-       mode <mode>,<mode>..<mode>
-       new file mode <mode>
-       deleted file mode <mode>,<mode>
++
+[synopsis]
+index <hash>,<hash>..<hash>
+mode <mode>,<mode>`..`<mode>
+new file mode <mode>
+deleted file mode <mode>,<mode>
 +
 The `mode <mode>,<mode>..<mode>` line appears only if at least one of
 the <mode> is different from the rest. Extended headers with
 information about detected content movement (renames and
 copying detection) are designed to work with the diff of two
-<tree-ish> and are not used by combined diff format.
+_<tree-ish>_ and are not used by combined diff format.
 
 3.   It is followed by a two-line from-file/to-file header: