git
diff --git a/‎MyFirstContribution.html
Lines changed: 1 addition & 1 deletion b/‎MyFirstContribution.html
Lines changed: 1 addition & 1 deletion
diff --git a/‎MyFirstObjectWalk.html
Lines changed: 1 addition & 1 deletion b/‎MyFirstObjectWalk.html
Lines changed: 1 addition & 1 deletion
diff --git a/‎RelNotes/2.46.0.txt
Lines changed: 63 additions & 1 deletion b/‎RelNotes/2.46.0.txt
Lines changed: 63 additions & 1 deletion
diff --git a/‎ReviewingGuidelines.html
Lines changed: 1 addition & 1 deletion b/‎ReviewingGuidelines.html
Lines changed: 1 addition & 1 deletion
diff --git a/‎SubmittingPatches.html
Lines changed: 10 additions & 8 deletions b/‎SubmittingPatches.html
Lines changed: 10 additions & 8 deletions
diff --git a/‎SubmittingPatches.txt
Lines changed: 8 additions & 6 deletions b/‎SubmittingPatches.txt
Lines changed: 8 additions & 6 deletions
diff --git a/‎ToolsForGit.html
Lines changed: 1 addition & 1 deletion b/‎ToolsForGit.html
Lines changed: 1 addition & 1 deletion
diff --git a/‎config.txt
Lines changed: 2 additions & 1 deletion b/‎config.txt
Lines changed: 2 additions & 1 deletion
diff --git a/‎everyday.html
Lines changed: 1 addition & 1 deletion b/‎everyday.html
Lines changed: 1 addition & 1 deletion
diff --git a/‎git-config.html
Lines changed: 2 additions & 1 deletion b/‎git-config.html
Lines changed: 2 additions & 1 deletion
@@ -735,7 +735,7 @@
 <body class="article">
 <div id="header">
 <h1>My First Contribution to the Git Project</h1>
-<span id="revdate">2024-04-30</span>
+<span id="revdate">2024-05-13</span>
 </div>
 <div id="content">
 <div class="sect1">
 
@@ -735,7 +735,7 @@
 <body class="article">
 <div id="header">
 <h1>My First Object Walk</h1>
-<span id="revdate">2024-04-30</span>
+<span id="revdate">2024-05-13</span>
 </div>
 <div id="content">
 <div class="sect1">
 
@@ -10,7 +10,22 @@ UI, Workflows & Features
  * The "--rfc" option of "git format-patch" learned to take an
    optional string value to be used in place of "RFC" to tweak the
    "[PATCH]" on the subject header.
-   (merge ce36894509 jc/format-patch-rfc-more later to maint).
+
+ * The credential helper protocol, together with the HTTP layer, have
+   been enhanced to support authentication schemes different from
+   username & password pair, like Bearer and NTLM.
+
+ * Command line completion script (in contrib/) learned to complete
+   "git symbolic-ref" a bit better (you need to enable plumbing
+   commands to be completed with GIT_COMPLETION_SHOW_ALL_COMMANDS).
+
+ * When the user responds to a prompt given by "git add -p" with an
+   unsupported command, list of available commands were given, which
+   was too much if the user knew what they wanted to type but merely
+   made a typo.  Now the user gets a much shorter error message.
+
+ * The color parsing code learned to handle 12-bit RGB colors, spelled
+   as "#RGB" (in addition to "#RRGGBB" that is already supported).
 
 
 Performance, Internal Implementation, Development Support etc.
@@ -23,6 +38,20 @@ Performance, Internal Implementation, Development Support etc.
    that are used in fuzzer tests, to make sure at least they build
    without bitrot, in Linux CI runs.
 
+ * Code to write out reftable has seen some optimization and
+   simplification.
+
+ * Tests to ensure interoperability between reftable written by jgit
+   and our code have been added and enabled in CI.
+
+ * The singleton index_state instance "the_index" has been eliminated
+   by always instantiating "the_repository" and replacing references
+   to "the_index"  with references to its .index member.
+
+
+ * Git-GUI has a new maintainer, Johannes Sixt.
+   (merge e18ad8eb26 jc/git-gui-maintainer-update later to maint).
+
 
 Fixes since v2.45
 -----------------
@@ -52,4 +81,37 @@ Fixes since v2.45
    errored out.  Now it keeps going.
    (merge c75662bfc9 js/for-each-repo-keep-going later to maint).
 
+ * zsh can pretend to be a normal shell pretty well except for some
+   glitches that we tickle in some of our scripts. Work them around
+   so that "vimdiff" and our test suite works well enough with it.
+   (merge fedd5c79ff bc/zsh-compatibility later to maint).
+
+ * Command line completion support for zsh (in contrib/) has been
+   updated to stop exposing internal state to end-user shell
+   interaction.
+   (merge 3c20acdf46 dk/zsh-git-repo-path-fix later to maint).
+
+ * Tests that try to corrupt in-repository files in chunked format did
+   not work well on macOS due to its broken "mv", which has been
+   worked around.
+   (merge 861dc19ba8 jc/test-workaround-broken-mv later to maint).
+
+ * The maximum size of attribute files is enforced more consistently.
+   (merge c793f9cb08 tb/attr-limits later to maint).
+
+ * Unbreak CI jobs so that we do not attempt to use Python 2 that has
+   been removed from the platform.
+   (merge 5ca0c455f1 ps/ci-python-2-deprecation later to maint).
+
+ * Git 2.43 started using the tree of HEAD as the source of attributes
+   in a bare repository, which has severe performance implications.
+   For now, revert the change, without ripping out a more explicit
+   support for the attr.tree configuration variable.
+   (merge 51441e6460 jc/no-default-attr-tree-in-bare later to maint).
+
  * Other code cleanup, docfix, build fix, etc.
+   (merge 4cf6e7bf5e jt/doc-submitting-rerolled-series later to maint).
+   (merge a5a4cb7b27 rs/diff-parseopts-cleanup later to maint).
+   (merge 395c130fd8 ma/win32-unix-domain-socket later to maint).
+   (merge 7df2405b38 jk/ci-macos-gcc13-fix later to maint).
+   (merge 55702c543e fa/p4-error later to maint).
@@ -735,7 +735,7 @@
 <body class="article">
 <div id="header">
 <h1>Reviewing Patches in the Git Project</h1>
-<span id="revdate">2024-04-30</span>
+<span id="revdate">2024-05-13</span>
 </div>
 <div id="content">
 <div class="sect1">
 
@@ -735,7 +735,7 @@
 <body class="article">
 <div id="header">
 <h1>Submitting Patches</h1>
-<span id="revdate">2024-04-30</span>
+<span id="revdate">2024-05-13</span>
 </div>
 <div id="content">
 <div class="sect1">
@@ -1257,10 +1257,12 @@ <h4 id="_code_format_patch_code_and_code_send_email_code"><code>format-patch</co
 e-mail tools, so that they may comment on specific portions of
 your code.  For this reason, each patch should be submitted
 "inline" in a separate message.</p></div>
-<div class="paragraph"><p>Multiple related patches should be grouped into their own e-mail
-thread to help readers find all parts of the series.  To that end,
-send them as replies to either an additional "cover letter" message
-(see below), the first patch, or the respective preceding patch.</p></div>
+<div class="paragraph"><p>All subsequent versions of a patch series and other related patches should be
+grouped into their own e-mail thread to help readers find all parts of the
+series.  To that end, send them as replies to either an additional "cover
+letter" message (see below), the first patch, or the respective preceding patch.
+Here is a <a href="MyFirstContribution.html#v2-git-send-email">step-by-step guide</a> on
+how to submit updated versions of a patch series.</p></div>
 <div class="paragraph"><p>If your log message (including your name on the
 <code>Signed-off-by</code> trailer) is not writable in ASCII, make sure that
 you send off a message in the correct encoding.</p></div>
@@ -1344,11 +1346,11 @@ <h2 id="_subsystems_with_dedicated_maintainers">Subsystems with dedicated mainta
 <div class="ulist"><ul>
 <li>
 <p>
-<code>git-gui/</code> comes from git-gui project, maintained by Pratyush Yadav:
+<code>git-gui/</code> comes from git-gui project, maintained by Johannes Sixt:
 </p>
 <div class="literalblock">
 <div class="content">
-<pre><code>https://github.com/prati0100/git-gui.git</code></pre>
+<pre><code>https://github.com/j6t/git-gui</code></pre>
 </div></div>
 </li>
 <li>
@@ -1580,7 +1582,7 @@ <h3 id="_gnus">Gnus</h3>
 <div id="footer">
 <div id="footer-text">
 Last updated
- 2024-05-01 10:56:52 PDT
+ 2024-05-13 12:26:57 PDT
 </div>
 </div>
 </body>
 
@@ -455,10 +455,12 @@ e-mail tools, so that they may comment on specific portions of
 your code.  For this reason, each patch should be submitted
 "inline" in a separate message.
 
-Multiple related patches should be grouped into their own e-mail
-thread to help readers find all parts of the series.  To that end,
-send them as replies to either an additional "cover letter" message
-(see below), the first patch, or the respective preceding patch.
+All subsequent versions of a patch series and other related patches should be
+grouped into their own e-mail thread to help readers find all parts of the
+series.  To that end, send them as replies to either an additional "cover
+letter" message (see below), the first patch, or the respective preceding patch.
+Here is a link:MyFirstContribution.html#v2-git-send-email[step-by-step guide] on
+how to submit updated versions of a patch series.
 
 If your log message (including your name on the
 `Signed-off-by` trailer) is not writable in ASCII, make sure that
@@ -543,9 +545,9 @@ not a text/plain, it's something else.
 Some parts of the system have dedicated maintainers with their own
 repositories.
 
-- `git-gui/` comes from git-gui project, maintained by Pratyush Yadav:
+- `git-gui/` comes from git-gui project, maintained by Johannes Sixt:
 
-	https://github.com/prati0100/git-gui.git
+        https://github.com/j6t/git-gui
 
 - `gitk-git/` comes from Paul Mackerras's gitk project:
 
 
@@ -735,7 +735,7 @@
 <body class="article">
 <div id="header">
 <h1>Tools for developing Git</h1>
-<span id="revdate">2024-04-30</span>
+<span id="revdate">2024-05-13</span>
 </div>
 <div id="content">
 <div class="sect1">
 
@@ -316,7 +316,8 @@ terminals, this is usually not the same as setting to "white black".
 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
 your terminal supports it, you may also specify 24-bit RGB values as
-hex, like `#ff0ab3`.
+hex, like `#ff0ab3`, or 12-bit RGB values like `#f1b`, which is
+equivalent to the 24-bit color `#ff11bb`.
 +
 The accepted attributes are `bold`, `dim`, `ul`, `blink`, `reverse`,
 `italic`, and `strike` (for crossed-out or "strikethrough" letters).
 
@@ -735,7 +735,7 @@
 <body class="article">
 <div id="header">
 <h1>Everyday Git With 20 Commands Or So</h1>
-<span id="revdate">2024-04-30</span>
+<span id="revdate">2024-05-13</span>
 </div>
 <div id="content">
 <div id="preamble">
 
@@ -1946,7 +1946,8 @@ <h3 id="_values">Values</h3>
 <div class="paragraph"><p>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
 your terminal supports it, you may also specify 24-bit RGB values as
-hex, like <code>#ff0ab3</code>.</p></div>
+hex, like <code>#ff0ab3</code>, or 12-bit RGB values like <code>#f1b</code>, which is
+equivalent to the 24-bit color <code>#ff11bb</code>.</p></div>
 <div class="paragraph"><p>The accepted attributes are <code>bold</code>, <code>dim</code>, <code>ul</code>, <code>blink</code>, <code>reverse</code>,
 <code>italic</code>, and <code>strike</code> (for crossed-out or "strikethrough" letters).
 The position of any attributes with respect to the colors