Autogenerated HTML docs for v2.49.0-634-g8613c

Author: gitster

RelNotes/2.50.0.adoc

@@ -65,6 +65,13 @@ UI, Workflows & Features
  * Make repository clean-up tasks "gc" can do available to "git
    maintenance" front-end.
 
+ * Bundle-URI feature did not use refs recorded in the bundle other
+   than normal branches as anchoring points to optimize the follow-up
+   fetch during "git clone"; now it is told to utilize all.
+
+ * The `send-email` documentation has been updated with OAuth2.0
+   related examples.
+
 
 Performance, Internal Implementation, Development Support etc.
 --------------------------------------------------------------
@@ -148,6 +155,8 @@ Performance, Internal Implementation, Development Support etc.
 
  * Further code clean-up in the object-store layer.
 
+ * Build performance fix.
+
 
 Fixes since v2.49
 -----------------
@@ -294,6 +303,9 @@ Fixes since v2.49
    derived systems use different errno, which has been worked around.
    (merge f47bcc3413 cf/wrapper-bsd-eloop later to maint).
 
+ * Use-after-free fix in the sequencer.
+   (merge 5dbaec628d pw/sequencer-reflog-use-after-free later to maint).
+
  * Other code cleanup, docfix, build fix, etc.
    (merge 227c4f33a0 ja/doc-block-delimiter-markup-fix later to maint).
    (merge 2bfd3b3685 ab/decorate-code-cleanup later to maint).
@@ -321,3 +333,6 @@ Fixes since v2.49
    (merge 42cf4ac552 ps/ci-resurrect-p4-on-github later to maint).
    (merge 104add8368 js/diff-codeql-false-positive-workaround later to maint).
    (merge f62977b93c en/get-tree-entry-doc later to maint).
+   (merge e5dd0a05ed ly/am-split-stgit-leakfix later to maint).
+   (merge bac220e154 rc/t1001-test-path-is-file later to maint).
+   (merge 91db6c735d ly/reftable-writer-leakfix later to maint).

git-send-email.adoc

@@ -509,12 +509,12 @@ include::includes/cmd-config-section-all.adoc[]
 
 include::config/sendemail.adoc[]
 
-EXAMPLES
---------
-Use gmail as the smtp server
+EXAMPLES OF SMTP SERVERS
+------------------------
+Use Gmail as the SMTP Server
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-To use 'git send-email' to send your patches through the GMail SMTP server,
-edit ~/.gitconfig to specify your account settings:
+To use `git send-email` to send your patches through the Gmail SMTP server,
+edit `~/.gitconfig` to specify your account settings:
 
 ----
 [sendemail]
@@ -528,6 +528,41 @@ If you have multi-factor authentication set up on your Gmail account, you can
 generate an app-specific password for use with 'git send-email'. Visit
 https://security.google.com/settings/security/apppasswords to create it.
 
+You can also use OAuth2.0 authentication with Gmail. `OAUTHBEARER` and
+`XOAUTH2` are common methods used for this type of authentication. Gmail
+supports both of them. As an example, if you want to use `OAUTHBEARER`, edit
+your `~/.gitconfig` file and add `smtpAuth = OAUTHBEARER` to your account
+settings:
+
+----
+[sendemail]
+	smtpEncryption = tls
+	smtpServer = smtp.gmail.com
+	smtpUser = [email protected]
+	smtpServerPort = 587
+	smtpAuth = OAUTHBEARER
+----
+
+Use Microsoft Outlook as the SMTP Server
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Unlike Gmail, Microsoft Outlook no longer supports app-specific passwords.
+Therefore, OAuth2.0 authentication must be used for Outlook. Also, it only
+supports `XOAUTH2` authentication method.
+
+Edit `~/.gitconfig` to specify your account settings for Outlook and use its
+SMTP server with `git send-email`:
+
+----
+[sendemail]
+	smtpEncryption = tls
+	smtpServer = smtp.office365.com
+	smtpUser = [email protected]
+	smtpServerPort = 587
+	smtpAuth = XOAUTH2
+----
+
+SENDING PATCHES
+---------------
 Once your commits are ready to be sent to the mailing list, run the
 following commands:
 
@@ -536,9 +571,25 @@ following commands:
 	$ git send-email outgoing/*
 
 The first time you run it, you will be prompted for your credentials.  Enter the
-app-specific or your regular password as appropriate.  If you have credential
-helper configured (see linkgit:git-credential[1]), the password will be saved in
-the credential store so you won't have to type it the next time.
+app-specific or your regular password as appropriate.
+
+If you have a credential helper configured (see linkgit:git-credential[1]), the
+password will be saved in the credential store so you won't have to type it the
+next time.
+
+If you are using OAuth2.0 authentication, you need to use an access token in
+place of a password when prompted. Various OAuth2.0 token generators are
+available online. Community maintained credential helpers for Gmail and Outlook
+are also available:
+
+	- https://github.com/AdityaGarg8/git-credential-email[git-credential-gmail]
+	  (cross platform, dedicated helper for authenticating Gmail accounts)
+
+	- https://github.com/AdityaGarg8/git-credential-email[git-credential-outlook]
+	  (cross platform, dedicated helper for authenticating Microsoft Outlook accounts)
+
+You can also see linkgit:gitcredentials[7] for more OAuth based authentication
+helpers.
 
 Note: the following core Perl modules that may be installed with your
 distribution of Perl are required:

git-send-email.html

@@ -1273,13 +1273,13 @@ <h2 id="_configuration">CONFIGURATION</h2>
 </div>
 </div>
 <div class="sect1">
-<h2 id="_examples">EXAMPLES</h2>
+<h2 id="_examples_of_smtp_servers">EXAMPLES OF SMTP SERVERS</h2>
 <div class="sectionbody">
 <div class="sect2">
-<h3 id="_use_gmail_as_the_smtp_server">Use gmail as the smtp server</h3>
+<h3 id="_use_gmail_as_the_smtp_server">Use Gmail as the SMTP Server</h3>
 <div class="paragraph">
-<p>To use <em>git send-email</em> to send your patches through the GMail SMTP server,
-edit ~/.gitconfig to specify your account settings:</p>
+<p>To use <code>git</code> <code>send-email</code> to send your patches through the Gmail SMTP server,
+edit <code>~/.gitconfig</code> to specify your account settings:</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -1296,6 +1296,51 @@ <h3 id="_use_gmail_as_the_smtp_server">Use gmail as the smtp server</h3>
 <a href="https://security.google.com/settings/security/apppasswords" class="bare">https://security.google.com/settings/security/apppasswords</a> to create it.</p>
 </div>
 <div class="paragraph">
+<p>You can also use OAuth2.0 authentication with Gmail. <code>OAUTHBEARER</code> and
+<code>XOAUTH2</code> are common methods used for this type of authentication. Gmail
+supports both of them. As an example, if you want to use <code>OAUTHBEARER</code>, edit
+your <code>~/.gitconfig</code> file and add <code>smtpAuth</code> <code>=</code> <code>OAUTHBEARER</code> to your account
+settings:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>[sendemail]
+        smtpEncryption = tls
+        smtpServer = smtp.gmail.com
+        smtpUser = [email protected]
+        smtpServerPort = 587
+        smtpAuth = OAUTHBEARER</pre>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_use_microsoft_outlook_as_the_smtp_server">Use Microsoft Outlook as the SMTP Server</h3>
+<div class="paragraph">
+<p>Unlike Gmail, Microsoft Outlook no longer supports app-specific passwords.
+Therefore, OAuth2.0 authentication must be used for Outlook. Also, it only
+supports <code>XOAUTH2</code> authentication method.</p>
+</div>
+<div class="paragraph">
+<p>Edit <code>~/.gitconfig</code> to specify your account settings for Outlook and use its
+SMTP server with <code>git</code> <code>send-email</code>:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>[sendemail]
+        smtpEncryption = tls
+        smtpServer = smtp.office365.com
+        smtpUser = [email protected]
+        smtpServerPort = 587
+        smtpAuth = XOAUTH2</pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_sending_patches">SENDING PATCHES</h2>
+<div class="sectionbody">
+<div class="paragraph">
 <p>Once your commits are ready to be sent to the mailing list, run the
 following commands:</p>
 </div>
@@ -1308,9 +1353,34 @@ <h3 id="_use_gmail_as_the_smtp_server">Use gmail as the smtp server</h3>
 </div>
 <div class="paragraph">
 <p>The first time you run it, you will be prompted for your credentials.  Enter the
-app-specific or your regular password as appropriate.  If you have credential
-helper configured (see <a href="git-credential.html">git-credential(1)</a>), the password will be saved in
-the credential store so you won&#8217;t have to type it the next time.</p>
+app-specific or your regular password as appropriate.</p>
+</div>
+<div class="paragraph">
+<p>If you have a credential helper configured (see <a href="git-credential.html">git-credential(1)</a>), the
+password will be saved in the credential store so you won&#8217;t have to type it the
+next time.</p>
+</div>
+<div class="paragraph">
+<p>If you are using OAuth2.0 authentication, you need to use an access token in
+place of a password when prompted. Various OAuth2.0 token generators are
+available online. Community maintained credential helpers for Gmail and Outlook
+are also available:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><a href="https://github.com/AdityaGarg8/git-credential-email">git-credential-gmail</a>
+(cross platform, dedicated helper for authenticating Gmail accounts)</p>
+</li>
+<li>
+<p><a href="https://github.com/AdityaGarg8/git-credential-email">git-credential-outlook</a>
+(cross platform, dedicated helper for authenticating Microsoft Outlook accounts)</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>You can also see <a href="gitcredentials.html">gitcredentials(7)</a> for more OAuth based authentication
+helpers.</p>
 </div>
 <div class="paragraph">
 <p>Note: the following core Perl modules that may be installed with your
@@ -1321,7 +1391,6 @@ <h3 id="_use_gmail_as_the_smtp_server">Use gmail as the smtp server</h3>
 </div>
 </div>
 </div>
-</div>
 <div class="sect1">
 <h2 id="_see_also">SEE ALSO</h2>
 <div class="sectionbody">
@@ -1341,7 +1410,7 @@ <h2 id="_git">GIT</h2>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2025-05-12 15:19:42 -0700
+Last updated 2025-05-20 15:10:14 -0700
 </div>
 </div>
 </body>

gitcredentials.adoc

@@ -133,6 +133,10 @@ Popular helpers with OAuth support include:
 
     - https://github.com/hickford/git-credential-oauth[git-credential-oauth] (cross platform, included in many Linux distributions)
 
+    - https://github.com/AdityaGarg8/git-credential-email[git-credential-gmail] (cross platform, dedicated helper to authenticate Gmail accounts for linkgit:git-send-email[1])
+
+    - https://github.com/AdityaGarg8/git-credential-email[git-credential-outlook] (cross platform, dedicated helper to authenticate Microsoft Outlook accounts for linkgit:git-send-email[1])
+
 CREDENTIAL CONTEXTS
 -------------------
 

gitcredentials.html

@@ -638,6 +638,12 @@ <h3 id="_oauth">OAuth</h3>
 <li>
 <p><a href="https://github.com/hickford/git-credential-oauth">git-credential-oauth</a> (cross platform, included in many Linux distributions)</p>
 </li>
+<li>
+<p><a href="https://github.com/AdityaGarg8/git-credential-email">git-credential-gmail</a> (cross platform, dedicated helper to authenticate Gmail accounts for <a href="git-send-email.html">git-send-email(1)</a>)</p>
+</li>
+<li>
+<p><a href="https://github.com/AdityaGarg8/git-credential-email">git-credential-outlook</a> (cross platform, dedicated helper to authenticate Microsoft Outlook accounts for <a href="git-send-email.html">git-send-email(1)</a>)</p>
+</li>
 </ul>
 </div>
 </div>
@@ -899,7 +905,7 @@ <h2 id="_git">GIT</h2>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2025-02-14 21:38:14 -0800
+Last updated 2025-05-20 15:10:14 -0700
 </div>
 </div>
 </body>

technical/bundle-uri.adoc

@@ -232,13 +232,13 @@ will interact with bundle URIs according to the following flow:
    are present in the client repository. If some are missing, then the
    client delays unbundling until other bundles have been unbundled,
    making those OIDs present. When all required OIDs are present, the
-   client unbundles that data using a refspec. The default refspec is
-   `+refs/heads/*:refs/bundles/*`, but this can be configured. These refs
-   are stored so that later `git fetch` negotiations can communicate each
-   bundled ref as a `have`, reducing the size of the fetch over the Git
-   protocol. To allow pruning refs from this ref namespace, Git may
-   introduce a numbered namespace (such as `refs/bundles/<i>/*`) such that
-   stale bundle refs can be deleted.
+   client unbundles that data using a refspec. The refspec used is
+   `+refs/*:refs/bundles/*`. These refs are stored so that later
+   `git fetch` negotiations can communicate each bundled ref as a `have`,
+   reducing the size of the fetch over the Git protocol. To allow pruning
+   refs from this ref namespace, Git may introduce a numbered namespace
+   (such as `refs/bundles/<i>/*`) such that stale bundle refs can be
+   deleted.
 
 3. If the file is instead a bundle list, then the client inspects the
    `bundle.mode` to see if the list is of the `all` or `any` form.

technical/bundle-uri.html

@@ -755,13 +755,13 @@ <h2 id="_cloning_with_bundle_uris">Cloning with Bundle URIs</h2>
 are present in the client repository. If some are missing, then the
 client delays unbundling until other bundles have been unbundled,
 making those OIDs present. When all required OIDs are present, the
-client unbundles that data using a refspec. The default refspec is
-<code>+refs/heads/*:refs/bundles/*</code>, but this can be configured. These refs
-are stored so that later <code>git</code> <code>fetch</code> negotiations can communicate each
-bundled ref as a <code>have</code>, reducing the size of the fetch over the Git
-protocol. To allow pruning refs from this ref namespace, Git may
-introduce a numbered namespace (such as <code>refs/bundles/</code><em>&lt;i&gt;</em><code>/*</code>) such that
-stale bundle refs can be deleted.</p>
+client unbundles that data using a refspec. The refspec used is
+<code>+refs/*:refs/bundles/*</code>. These refs are stored so that later
+<code>git</code> <code>fetch</code> negotiations can communicate each bundled ref as a <code>have</code>,
+reducing the size of the fetch over the Git protocol. To allow pruning
+refs from this ref namespace, Git may introduce a numbered namespace
+(such as <code>refs/bundles/</code><em>&lt;i&gt;</em><code>/*</code>) such that stale bundle refs can be
+deleted.</p>
 </li>
 <li>
 <p>If the file is instead a bundle list, then the client inspects the
@@ -1218,7 +1218,7 @@ <h2 id="_see_also">See Also</h2>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2025-02-14 21:38:14 -0800
+Last updated 2025-05-20 15:10:14 -0700
 </div>
 </div>
 </body>