Autogenerated HTML docs for v2.50.0-81-gcb3b4

Author: gitster

MyFirstObjectWalk.adoc

@@ -43,7 +43,7 @@ Open up a new file `builtin/walken.c` and set up the command handler:
 #include "builtin.h"
 #include "trace.h"
 
-int cmd_walken(int argc, const char **argv, const char *prefix)
+int cmd_walken(int argc, const char **argv, const char *prefix, struct repository *repo)
 {
 	trace_printf(_("cmd_walken incoming...\n"));
 	return 0;
@@ -86,7 +86,7 @@ int cmd_walken(int argc, const char **argv, const char *prefix)
 Also add the relevant line in `builtin.h` near `cmd_whatchanged()`:
 
 ----
-int cmd_walken(int argc, const char **argv, const char *prefix);
+int cmd_walken(int argc, const char **argv, const char *prefix, struct repository *repo);
 ----
 
 Include the command in `git.c` in `commands[]` near the entry for `whatchanged`,
@@ -96,10 +96,23 @@ maintaining alphabetical ordering:
 { "walken", cmd_walken, RUN_SETUP },
 ----
 
-Add it to the `Makefile` near the line for `builtin/worktree.o`:
+Add an entry for the new command in the both the Make and Meson build system,
+before the entry for `worktree`:
 
+- In the `Makefile`:
 ----
+...
 BUILTIN_OBJS += builtin/walken.o
+...
+----
+
+- In the `meson.build` file:
+----
+builtin_sources = [
+   ...
+  'builtin/walken.c',
+   ...
+]
 ----
 
 Build and test out your command, without forgetting to ensure the `DEVELOPER`
@@ -193,7 +206,7 @@ initialization functions.
 
 Next, we should have a look at any relevant configuration settings (i.e.,
 settings readable and settable from `git config`). This is done by providing a
-callback to `git_config()`; within that callback, you can also invoke methods
+callback to `repo_config()`; within that callback, you can also invoke methods
 from other components you may need that need to intercept these options. Your
 callback will be invoked once per each configuration value which Git knows about
 (global, local, worktree, etc.).
@@ -221,14 +234,14 @@ static int git_walken_config(const char *var, const char *value,
 }
 ----
 
-Make sure to invoke `git_config()` with it in your `cmd_walken()`:
+Make sure to invoke `repo_config()` with it in your `cmd_walken()`:
 
 ----
-int cmd_walken(int argc, const char **argv, const char *prefix)
+int cmd_walken(int argc, const char **argv, const char *prefix, struct repository *repo)
 {
 	...
 
-	git_config(git_walken_config, NULL);
+	repo_config(repo, git_walken_config, NULL);
 
 	...
 }
@@ -250,14 +263,14 @@ We'll also need to include the `revision.h` header:
 
 ...
 
-int cmd_walken(int argc, const char **argv, const char *prefix)
+int cmd_walken(int argc, const char **argv, const char *prefix, struct repository *repo)
 {
 	/* This can go wherever you like in your declarations.*/
 	struct rev_info rev;
 	...
 
-	/* This should go after the git_config() call. */
-	repo_init_revisions(the_repository, &rev, prefix);
+	/* This should go after the repo_config() call. */
+	repo_init_revisions(repo, &rev, prefix);
 
 	...
 }
@@ -305,7 +318,7 @@ Then let's invoke `final_rev_info_setup()` after the call to
 `repo_init_revisions()`:
 
 ----
-int cmd_walken(int argc, const char **argv, const char *prefix)
+int cmd_walken(int argc, const char **argv, const char *prefix, struct repository *repo)
 {
 	...
 

MyFirstObjectWalk.html

@@ -507,7 +507,7 @@ <h2 id="_setting_up">Setting Up</h2>
 #include "builtin.h"
 #include "trace.h"
 
-int cmd_walken(int argc, const char **argv, const char *prefix)
+int cmd_walken(int argc, const char **argv, const char *prefix, struct repository *repo)
 {
         trace_printf(_("cmd_walken incoming...\n"));
         return 0;
@@ -564,7 +564,7 @@ <h2 id="_setting_up">Setting Up</h2>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre>int cmd_walken(int argc, const char **argv, const char *prefix);</pre>
+<pre>int cmd_walken(int argc, const char **argv, const char *prefix, struct repository *repo);</pre>
 </div>
 </div>
 <div class="paragraph">
@@ -577,11 +577,37 @@ <h2 id="_setting_up">Setting Up</h2>
 </div>
 </div>
 <div class="paragraph">
-<p>Add it to the <code>Makefile</code> near the line for <code>builtin/worktree.o</code>:</p>
+<p>Add an entry for the new command in the both the Make and Meson build system,
+before the entry for <code>worktree</code>:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>In the <code>Makefile</code>:</p>
+</li>
+</ul>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>...
+BUILTIN_OBJS += builtin/walken.o
+...</pre>
+</div>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>In the <code>meson.build</code> file:</p>
+</li>
+</ul>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre>BUILTIN_OBJS += builtin/walken.o</pre>
+<pre>builtin_sources = [
+   ...
+  'builtin/walken.c',
+   ...
+]</pre>
 </div>
 </div>
 <div class="paragraph">
@@ -734,7 +760,7 @@ <h4 id="_configuring_from_gitconfig">Configuring From .<code>gitconfig</code></h
 <div class="paragraph">
 <p>Next, we should have a look at any relevant configuration settings (i.e.,
 settings readable and settable from <code>git</code> <code>config</code>). This is done by providing a
-callback to <code>git_config</code>(); within that callback, you can also invoke methods
+callback to <code>repo_config</code>(); within that callback, you can also invoke methods
 from other components you may need that need to intercept these options. Your
 callback will be invoked once per each configuration value which Git knows about
 (global, local, worktree, etc.).</p>
@@ -766,15 +792,15 @@ <h4 id="_configuring_from_gitconfig">Configuring From .<code>gitconfig</code></h
 </div>
 </div>
 <div class="paragraph">
-<p>Make sure to invoke <code>git_config</code>() with it in your <code>cmd_walken</code>():</p>
+<p>Make sure to invoke <code>repo_config</code>() with it in your <code>cmd_walken</code>():</p>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre>int cmd_walken(int argc, const char **argv, const char *prefix)
+<pre>int cmd_walken(int argc, const char **argv, const char *prefix, struct repository *repo)
 {
         ...
 
-        git_config(git_walken_config, NULL);
+        repo_config(repo, git_walken_config, NULL);
 
         ...
 }</pre>
@@ -800,14 +826,14 @@ <h4 id="_setting_up_rev_info">Setting Up <code>rev_info</code></h4>
 
 ...
 
-int cmd_walken(int argc, const char **argv, const char *prefix)
+int cmd_walken(int argc, const char **argv, const char *prefix, struct repository *repo)
 {
         /* This can go wherever you like in your declarations.*/
         struct rev_info rev;
         ...
 
-        /* This should go after the git_config() call. */
-        repo_init_revisions(the_repository, &amp;rev, prefix);
+        /* This should go after the repo_config() call. */
+        repo_init_revisions(repo, &amp;rev, prefix);
 
         ...
 }</pre>
@@ -871,7 +897,7 @@ <h4 id="_tweaking_rev_info_for_the_walk">Tweaking <code>rev_info</code> For the
 </div>
 <div class="listingblock">
 <div class="content">
-<pre>int cmd_walken(int argc, const char **argv, const char *prefix)
+<pre>int cmd_walken(int argc, const char **argv, const char *prefix, struct repository *repo)
 {
         ...
 
@@ -1675,7 +1701,7 @@ <h2 id="_wrapping_up">Wrapping Up</h2>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2025-03-26 00:41:02 -0700
+Last updated 2025-06-18 14:54:41 -0700
 </div>
 </div>
 </body>

RelNotes/2.51.0.adoc

@@ -0,0 +1,58 @@
+Git v2.51 Release Notes
+=======================
+
+UI, Workflows & Features
+------------------------
+
+ * Userdiff patterns for the R language have been added.
+
+ * Documentation for "git send-email" has been updated with a bit more
+   credential helper and OAuth information.
+
+ * "git cat-file --batch" learns to understand %(objectmode) atom to
+   allow the caller to tell missing objects (due to repository
+   corruption) and submodules (whose commit objects are OK to be
+   missing) apart.
+
+ * "git diff --no-index dirA dirB" can limit the comparison with
+   pathspec at the end of the command line, just like normal "git
+   diff".
+
+
+Performance, Internal Implementation, Development Support etc.
+--------------------------------------------------------------
+
+ * "git pack-objects" learned to find delta bases from blobs at the
+   same path, using the --path-walk API.
+
+ * CodingGuidelines update.
+
+ * Add settings for Solaris 10 & 11.
+
+ * Meson-based build/test framework now understands TAP output
+   generated by our tests.
+
+
+Fixes since v2.50
+-----------------
+
+ * A memory-leak in an error code path has been plugged.
+   (merge 7082da85cb ly/commit-graph-graph-write-leakfix later to maint).
+
+ * A memory-leak in an error code path has been plugged.
+   (merge aedebdb6b9 ly/fetch-pack-leakfix later to maint).
+
+ * Some leftover references to documentation source files that no
+   longer exist, due to recent ".txt" -> ".adoc" renaming, have been
+   corrected.
+   (merge 3717a5775a jw/doc-txt-to-adoc-refs later to maint).
+
+ * Other code cleanup, docfix, build fix, etc.
+   (merge b257adb571 lo/my-first-ow-doc-update later to maint).
+   (merge 8b34b6a220 ly/sequencer-update-squash-is-fixup-only later to maint).
+   (merge 5dceb8bd05 ly/do-not-localize-bug-messages later to maint).
+   (merge 61372dd613 ly/commit-buffer-reencode-leakfix later to maint).
+   (merge 81cd1eef7d ly/pack-bitmap-root-leakfix later to maint).
+   (merge bfc9f9cc64 ly/submodule-update-failure-leakfix later to maint).
+   (merge 65dff89c6b ma/doc-diff-cc-headers later to maint).
+   (merge efb61591ee jm/bundle-uri-debug-output-to-fp later to maint).

diff-generate-patch.adoc

@@ -138,7 +138,7 @@ or like this (when the `--cc` option is used):
 +
 [synopsis]
 index <hash>,<hash>..<hash>
-mode <mode>,<mode>`..`<mode>
+mode <mode>,<mode>..<mode>
 new file mode <mode>
 deleted file mode <mode>,<mode>
 +

git-cat-file.adoc

@@ -307,6 +307,11 @@ newline. The available atoms are:
 `objecttype`::
 	The type of the object (the same as `cat-file -t` reports).
 
+`objectmode`::
+	If the specified object has mode information (such as a tree or
+	index entry), the mode expressed as an octal integer. Otherwise,
+	empty string.
+
 `objectsize`::
 	The size, in bytes, of the object (the same as `cat-file -s`
 	reports).
@@ -368,6 +373,14 @@ If a name is specified that might refer to more than one object (an ambiguous sh
 <object> SP ambiguous LF
 ------------
 
+If a name is specified that refers to a submodule entry in a tree and the
+target object does not exist in the repository, then `cat-file` will ignore
+any custom format and print (with the object ID of the submodule):
+
+------------
+<oid> SP submodule LF
+------------
+
 If `--follow-symlinks` is used, and a symlink in the repository points
 outside the repository, then `cat-file` will ignore any custom format
 and print:

git-cat-file.html

@@ -867,6 +867,12 @@ <h2 id="_batch_output">BATCH OUTPUT</h2>
 <dd>
 <p>The type of the object (the same as <code>cat-file</code> <code>-t</code> reports).</p>
 </dd>
+<dt class="hdlist1"><code>objectmode</code></dt>
+<dd>
+<p>If the specified object has mode information (such as a tree or
+index entry), the mode expressed as an octal integer. Otherwise,
+empty string.</p>
+</dd>
 <dt class="hdlist1"><code>objectsize</code></dt>
 <dd>
 <p>The size, in bytes, of the object (the same as <code>cat-file</code> <code>-s</code>
@@ -947,6 +953,16 @@ <h2 id="_batch_output">BATCH OUTPUT</h2>
 </div>
 </div>
 <div class="paragraph">
+<p>If a name is specified that refers to a submodule entry in a tree and the
+target object does not exist in the repository, then <code>cat-file</code> will ignore
+any custom format and print (with the object ID of the submodule):</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>&lt;oid&gt; SP submodule LF</pre>
+</div>
+</div>
+<div class="paragraph">
 <p>If <code>--follow-symlinks</code> is used, and a symlink in the repository points
 outside the repository, then <code>cat-file</code> will ignore any custom format
 and print:</p>
@@ -1041,7 +1057,7 @@ <h2 id="_git">GIT</h2>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2025-05-27 15:29:51 -0700
+Last updated 2025-06-18 14:54:41 -0700
 </div>
 </div>
 </body>