Update 2 packages

mingw-w64-i686-git (2.49.0.rc1.windows.1-1 -> 2.49.0.rc2.windows.1-1)
mingw-w64-i686-git-doc-html (2.49.0.rc1.windows.1-1 -> 2.49.0.rc2.windows.1-1)

Signed-off-by: Git for Windows Build Agent <[email protected]>

Author: Git for Windows Build Agent

cmd/git-gui.exe

@@ -69,7 +69,7 @@ use File::Path qw/rmtree/;
 use File::Basename;
 use Getopt::Long qw(:config require_order no_ignore_case);
 
-my $VERSION = '2.49.0.rc1.windows.1';
+my $VERSION = '2.49.0.rc2.windows.1';
 
 my $log = GITCVS::log->new();
 my $cfg;

cmd/git-receive-pack.exe

@@ -69,7 +69,7 @@ use File::Path qw/rmtree/;
 use File::Basename;
 use Getopt::Long qw(:config require_order no_ignore_case);
 
-my $VERSION = '2.49.0.rc1.windows.1';
+my $VERSION = '2.49.0.rc2.windows.1';
 
 my $log = GITCVS::log->new();
 my $cfg;

cmd/git-upload-pack.exe

@@ -1544,7 +1544,7 @@ sub gen_header {
 	@recipients = unique_email_list(@recipients,@cc,@initial_bcc);
 	@recipients = (map { extract_valid_address_or_die($_) } @recipients);
 	my $date = format_2822_time($time++);
-	my $gitversion = '2.49.0.rc1.windows.1';
+	my $gitversion = '2.49.0.rc2.windows.1';
 	if ($gitversion =~ m/..GIT_VERSION../) {
 	    $gitversion = Git::version();
 	}

cmd/git.exe

@@ -52,7 +52,7 @@ use vars qw/	$AUTHOR $VERSION
 		$_revision $_repository
 		$_q $_authors $_authors_prog %users/;
 $AUTHOR = 'Eric Wong <[email protected]>';
-$VERSION = '2.49.0.rc1.windows.1';
+$VERSION = '2.49.0.rc2.windows.1';
 
 use Carp qw/croak/;
 use File::Basename qw/dirname basename/;

cmd/gitk.exe

@@ -538,7 +538,7 @@ <h2 id="_other_discussion_venues">Other Discussion Venues</h2>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2025-03-05 13:23:01 UTC
+Last updated 2025-03-11 08:30:44 UTC
 </div>
 </div>
 </body>

cmd/scalar.exe

@@ -470,7 +470,7 @@ <h3 id="related-reading"><a class="anchor" href="#related-reading"></a>Related R
 <p><code>Documentation/SubmittingPatches</code></p>
 </li>
 <li>
-<p><code>Documentation/howto/new-command.txt</code></p>
+<p><code>Documentation/howto/new-command.adoc</code></p>
 </li>
 </ul>
 </div>
@@ -870,7 +870,7 @@ <h3 id="implementation"><a class="anchor" href="#implementation"></a>Implementat
 apply standard precedence rules. <code>git_config_get_string_tmp</code>() will look up
 a specific key ("user.name") and give you the value. There are a number of
 single-key lookup functions like this one; you can see them all (and more info
-about how to use <code>git_config</code>()) in <code>Documentation/technical/api-config.txt</code>.</p>
+about how to use <code>git_config</code>()) in <code>Documentation/technical/api-config.adoc</code>.</p>
 </div>
 <div class="paragraph">
 <p>You should see that the name printed matches the one you see when you run:</p>
@@ -1041,10 +1041,10 @@ <h3 id="add-documentation"><a class="anchor" href="#add-documentation"></a>Addin
 <p>Your new command is undocumented! Let&#8217;s fix that.</p>
 </div>
 <div class="paragraph">
-<p>Take a look at <code>Documentation/git-</code>*.<code>txt</code>. These are the manpages for the
+<p>Take a look at <code>Documentation/git-</code>*.<code>adoc</code>. These are the manpages for the
 subcommands that Git knows about. You can open these up and take a look to get
 acquainted with the format, but then go ahead and make a new file
-<code>Documentation/git-psuh.txt</code>. Like with most of the documentation in the Git
+<code>Documentation/git-psuh.adoc</code>. Like with most of the documentation in the Git
 project, help pages are written with AsciiDoc (see CodingGuidelines, "Writing
 Documentation" section). Use the following template to fill out your own
 manpage:</p>
@@ -1142,7 +1142,7 @@ <h3 id="add-usage"><a class="anchor" href="#add-usage"></a>Adding Usage Text</h3
 printing usage.</p>
 </div>
 <div class="paragraph">
-<p>Take a look at <code>Documentation/technical/api-parse-options.txt</code>. This is a handy
+<p>Take a look at <code>Documentation/technical/api-parse-options.adoc</code>. This is a handy
 tool for pulling out options you need to be able to handle, and it takes a
 usage string.</p>
 </div>
@@ -1847,14 +1847,14 @@ <h3 id="preparing-cover-letter"><a class="anchor" href="#preparing-cover-letter"
 </div>
 <div class="listingblock">
 <div class="content">
-<pre> Documentation/git-psuh.txt | 40 +++++++++++++++++++++
- Makefile                   |  1 +
- builtin.h                  |  1 +
- builtin/psuh.c             | 73 ++++++++++++++++++++++++++++++++++++++
- git.c                      |  1 +
- t/t9999-psuh-tutorial.sh   | 12 +++++++
+<pre> Documentation/git-psuh.adoc | 40 +++++++++++++++++++++
+ Makefile                    |  1 +
+ builtin.h                   |  1 +
+ builtin/psuh.c              | 73 ++++++++++++++++++++++++++++++++++++++
+ git.c                       |  1 +
+ t/t9999-psuh-tutorial.sh    | 12 +++++++
  6 files changed, 128 insertions(+)
- create mode 100644 Documentation/git-psuh.txt
+ create mode 100644 Documentation/git-psuh.adoc
  create mode 100644 builtin/psuh.c
  create mode 100755 t/t9999-psuh-tutorial.sh</pre>
 </div>
@@ -2239,7 +2239,7 @@ <h3 id="after-approval"><a class="anchor" href="#after-approval"></a>After Revie
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2025-03-05 13:23:01 UTC
+Last updated 2025-03-11 08:30:44 UTC
 </div>
 </div>
 </body>

cmd/tig.exe

@@ -465,7 +465,7 @@ <h3 id="_related_reading">Related Reading</h3>
 <div class="ulist">
 <ul>
 <li>
-<p><code>Documentation/user-manual.txt</code> under "Hacking Git" contains some coverage of
+<p><code>Documentation/user-manual.adoc</code> under "Hacking Git" contains some coverage of
 the revision walker in its various incarnations.</p>
 </li>
 <li>
@@ -603,7 +603,7 @@ <h2 id="_setting_up">Setting Up</h2>
 </td>
 <td class="content">
 For a more exhaustive overview of the new command process, take a look at
-<code>Documentation/MyFirstContribution.txt</code>.
+<code>Documentation/MyFirstContribution.adoc</code>.
 </td>
 </tr>
 </table>
@@ -642,7 +642,7 @@ <h3 id="_struct_rev_cmdline_info"><code>struct</code> <code>rev_cmdline_info</co
 </div>
 <div class="paragraph">
 <p><code>item</code> is the object provided upon which to base the object walk. Items in Git
-can be blobs, trees, commits, or tags. (See <code>Documentation/gittutorial-2.txt</code>.)</p>
+can be blobs, trees, commits, or tags. (See <code>Documentation/gittutorial-2.adoc</code>.)</p>
 </div>
 <div class="paragraph">
 <p><code>name</code> is the object ID (OID) of the object - a hex string you may be familiar
@@ -653,7 +653,7 @@ <h3 id="_struct_rev_cmdline_info"><code>struct</code> <code>rev_cmdline_info</co
 <div class="paragraph">
 <p><code>whence</code> indicates some information about what to do with the parents of the
 specified object. We&#8217;ll explore this flag more later on; take a look at
-<code>Documentation/revisions.txt</code> to get an idea of what could set the <code>whence</code>
+<code>Documentation/revisions.adoc</code> to get an idea of what could set the <code>whence</code>
 value.</p>
 </div>
 <div class="paragraph">
@@ -668,7 +668,7 @@ <h3 id="_struct_rev_info"><code>struct</code> <code>rev_info</code></h3>
 <div class="paragraph">
 <p>This one is quite a bit longer, and many fields are only used during the walk
 by <code>revision.c</code> - not configuration options. Most of the configurable flags in
-<code>struct</code> <code>rev_info</code> have a mirror in <code>Documentation/rev-list-options.txt</code>. It&#8217;s a
+<code>struct</code> <code>rev_info</code> have a mirror in <code>Documentation/rev-list-options.adoc</code>. It&#8217;s a
 good idea to take some time and read through that document.</p>
 </div>
 </div>
@@ -1428,7 +1428,7 @@ <h2 id="_basic_object_walk">Basic Object Walk</h2>
 <h3 id="_adding_a_filter_2">Adding a Filter</h3>
 <div class="paragraph">
 <p>There are a handful of filters that we can apply to the object walk laid out in
-<code>Documentation/rev-list-options.txt</code>. These filters are typically useful for
+<code>Documentation/rev-list-options.adoc</code>. These filters are typically useful for
 operations such as creating packfiles or performing a partial clone. They are
 defined in <code>list-objects-filter-options.h</code>. For the purposes of this tutorial we
 will use the "tree:1" filter, which causes the walk to omit all trees and blobs
@@ -1675,7 +1675,7 @@ <h2 id="_wrapping_up">Wrapping Up</h2>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2025-03-05 13:23:01 UTC
+Last updated 2025-03-11 08:30:44 UTC
 </div>
 </div>
 </body>

etc/rebase.db.i386

@@ -683,7 +683,7 @@ <h2 id="_see_also">See Also</h2>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2025-03-05 13:23:01 UTC
+Last updated 2025-03-11 08:30:44 UTC
 </div>
 </div>
 </body>

git-bash.exe

@@ -1584,7 +1584,7 @@ <h3 id="_gnus">Gnus</h3>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2025-03-05 13:23:01 UTC
+Last updated 2025-03-11 08:30:44 UTC
 </div>
 </div>
 </body>

git-cmd.exe

@@ -520,7 +520,7 @@ <h4 id="_httpswww_kernel_orgdochtmlv4_10processcoding_style_htmlyou_ve_made_a_me
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2025-03-05 13:23:01 UTC
+Last updated 2025-03-11 08:30:44 UTC
 </div>
 </div>
 </body>

mingw32/bin/git-cvsserver

@@ -457,7 +457,7 @@ <h1>Everyday Git With 20 Commands Or So</h1>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2025-03-05 13:23:01 UTC
+Last updated 2025-03-11 08:30:44 UTC
 </div>
 </div>
 </body>

mingw32/bin/git-receive-pack.exe

@@ -1030,7 +1030,7 @@ <h2 id="_git">GIT</h2>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2025-03-05 13:23:01 UTC
+Last updated 2025-03-11 08:30:44 UTC
 </div>
 </div>
 </body>