Autogenerated HTML docs for v2.49.0-654-g845c4

Author: gitster

RelNotes/2.50.0.adoc

@@ -72,6 +72,10 @@ UI, Workflows & Features
  * The `send-email` documentation has been updated with OAuth2.0
    related examples.
 
+ * Two of the "scalar" subcommands that add a repository that hasn't
+   been under "scalar"'s control are taught an option not to enable the
+   scheduled maintenance on it.
+
 
 Performance, Internal Implementation, Development Support etc.
 --------------------------------------------------------------
@@ -157,6 +161,12 @@ Performance, Internal Implementation, Development Support etc.
 
  * Build performance fix.
 
+ * Teach "git send-email" to also consult `hostname -f` for mail
+   domain to compute the identity given to SMTP servers.
+
+ * The dependency on the_repository variable has been reduced from the
+   code paths in "git replay".
+
 
 Fixes since v2.49
 -----------------
@@ -306,6 +316,15 @@ Fixes since v2.49
  * Use-after-free fix in the sequencer.
    (merge 5dbaec628d pw/sequencer-reflog-use-after-free later to maint).
 
+ * win+Meson CI pipeline, unlike other pipelines for Windows,
+   used to build artifacts in develper mode, which has been changed to
+   build them in release mode for consistency.
+   (merge 184abdcf05 js/ci-build-win-in-release-mode later to maint).
+
+ * CI settings at GitLab has been updated to run MSVC based Meson job
+   automatically (as opposed to be done only upon manual request).
+   (merge 6389579b2f ps/ci-gitlab-enable-msvc-meson-job 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).

scalar.adoc

@@ -9,12 +9,12 @@ SYNOPSIS
 --------
 [verse]
 scalar clone [--single-branch] [--branch <main-branch>] [--full-clone]
-	[--[no-]src] <url> [<enlistment>]
+	[--[no-]src] [--[no-]tags] [--[no-]maintenance] <url> [<enlistment>]
 scalar list
-scalar register [<enlistment>]
+scalar register [--[no-]maintenance] [<enlistment>]
 scalar unregister [<enlistment>]
 scalar run ( all | config | commit-graph | fetch | loose-objects | pack-files ) [<enlistment>]
-scalar reconfigure [ --all | <enlistment> ]
+scalar reconfigure [--maintenance=(enable|disable|keep)] [ --all | <enlistment> ]
 scalar diagnose [<enlistment>]
 scalar delete <enlistment>
 
@@ -97,6 +97,11 @@ cloning. If the HEAD at the remote did not point at any branch when
 	A sparse-checkout is initialized by default. This behavior can be
 	turned off via `--full-clone`.
 
+--[no-]maintenance::
+	By default, `scalar clone` configures the enlistment to use Git's
+	background maintenance feature. Use the `--no-maintenance` to skip
+	this configuration.
+
 List
 ~~~~
 
@@ -117,6 +122,12 @@ Note: when this subcommand is called in a worktree that is called `src/`, its
 parent directory is considered to be the Scalar enlistment. If the worktree is
 _not_ called `src/`, it itself will be considered to be the Scalar enlistment.
 
+--[no-]maintenance::
+	By default, `scalar register` configures the enlistment to use Git's
+	background maintenance feature. Use the `--no-maintenance` to skip
+	this configuration. This does not disable any maintenance that may
+	already be enabled in other ways.
+
 Unregister
 ~~~~~~~~~~
 
@@ -149,8 +160,18 @@ After a Scalar upgrade, or when the configuration of a Scalar enlistment
 was somehow corrupted or changed by mistake, this subcommand allows to
 reconfigure the enlistment.
 
-With the `--all` option, all enlistments currently registered with Scalar
-will be reconfigured. Use this option after each Scalar upgrade.
+--all::
+	When `--all` is specified, reconfigure all enlistments currently
+	registered with Scalar by the `scalar.repo` config key. Use this
+	option after each upgrade to get the latest features.
+
+--maintenance=(enable|disable|keep)::
+	By default, Scalar configures the enlistment to use Git's
+	background maintenance feature; this is the same as using the
+	`enable` value for this option. Use the	`disable` value to
+	remove each considered enlistment from background maintenance.
+	Use `keep' to leave the background maintenance configuration
+	untouched for these repositories.
 
 Diagnose
 ~~~~~~~~

scalar.html

@@ -453,12 +453,12 @@ <h2 id="_synopsis">SYNOPSIS</h2>
 <div class="sectionbody">
 <div class="verseblock">
 <pre class="content">scalar clone [--single-branch] [--branch &lt;main-branch&gt;] [--full-clone]
-        [--[no-]src] &lt;url&gt; [&lt;enlistment&gt;]
+        [--[no-]src] [--[no-]tags] [--[no-]maintenance] &lt;url&gt; [&lt;enlistment&gt;]
 scalar list
-scalar register [&lt;enlistment&gt;]
+scalar register [--[no-]maintenance] [&lt;enlistment&gt;]
 scalar unregister [&lt;enlistment&gt;]
 scalar run ( all | config | commit-graph | fetch | loose-objects | pack-files ) [&lt;enlistment&gt;]
-scalar reconfigure [ --all | &lt;enlistment&gt; ]
+scalar reconfigure [--maintenance=(enable|disable|keep)] [ --all | &lt;enlistment&gt; ]
 scalar diagnose [&lt;enlistment&gt;]
 scalar delete &lt;enlistment&gt;</pre>
 </div>
@@ -564,6 +564,12 @@ <h3 id="_clone">Clone</h3>
 <p>A sparse-checkout is initialized by default. This behavior can be
 turned off via <code>--full-clone</code>.</p>
 </dd>
+<dt class="hdlist1">--[no-]maintenance</dt>
+<dd>
+<p>By default, <code>scalar</code> <code>clone</code> configures the enlistment to use Git&#8217;s
+background maintenance feature. Use the <code>--no-maintenance</code> to skip
+this configuration.</p>
+</dd>
 </dl>
 </div>
 </div>
@@ -595,6 +601,13 @@ <h3 id="_register">Register</h3>
 <em>not</em> called <code>src/</code>, it itself will be considered to be the Scalar enlistment.</p>
 </div>
 </dd>
+<dt class="hdlist1">--[no-]maintenance</dt>
+<dd>
+<p>By default, <code>scalar</code> <code>register</code> configures the enlistment to use Git&#8217;s
+background maintenance feature. Use the <code>--no-maintenance</code> to skip
+this configuration. This does not disable any maintenance that may
+already be enabled in other ways.</p>
+</dd>
 </dl>
 </div>
 </div>
@@ -642,9 +655,24 @@ <h3 id="_reconfigure">Reconfigure</h3>
 was somehow corrupted or changed by mistake, this subcommand allows to
 reconfigure the enlistment.</p>
 </div>
-<div class="paragraph">
-<p>With the <code>--all</code> option, all enlistments currently registered with Scalar
-will be reconfigured. Use this option after each Scalar upgrade.</p>
+<div class="dlist">
+<dl>
+<dt class="hdlist1">--all</dt>
+<dd>
+<p>When <code>--all</code> is specified, reconfigure all enlistments currently
+registered with Scalar by the <code>scalar.repo</code> config key. Use this
+option after each upgrade to get the latest features.</p>
+</dd>
+<dt class="hdlist1">--maintenance=(enable|disable|keep)</dt>
+<dd>
+<p>By default, Scalar configures the enlistment to use Git&#8217;s
+background maintenance feature; this is the same as using the
+<code>enable</code> value for this option. Use the	<code>disable</code> value to
+remove each considered enlistment from background maintenance.
+Use &#8216;keep&#8217; to leave the background maintenance configuration
+untouched for these repositories.</p>
+</dd>
+</dl>
 </div>
 </div>
 <div class="sect2">
@@ -697,7 +725,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-23 17:05:02 -0700
 </div>
 </div>
 </body>