From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2025, #08; Mon, 23)
Date: Tue, 24 Jun 2025 12:01:46 -0700 [thread overview]
Message-ID: <xmqqqzz9yndx.fsf@gitster.g> (raw)
In-Reply-To: <xmqqtt462bye.fsf@gitster.g> (Junio C. Hamano's message of "Mon, 23 Jun 2025 17:57:29 -0700")
Here are the topics that gradulated to the 'master' branch lately.
* ac/preload-index-wo-the-repository (2025-06-10) 2 commits
* ag/send-email-edit-threading-fix (2025-06-04) 2 commits
* jc/cg-let-bss-do-its-job (2025-06-11) 1 commit
* kj/stash-onbranch-submodule-fix (2025-06-10) 1 commit
* ly/prepare-show-merge-leakfix (2025-06-09) 1 commit
* ly/run-builtin-use-passed-in-repo (2025-06-15) 1 commit
* pw/stash-p-pathspec-fixes (2025-06-07) 2 commits
* pw/subtree-gpg-sign (2025-06-04) 2 commits
* rm/t2400-modernize (2025-06-16) 1 commit
* sa/multi-mailmap-fix (2025-06-13) 1 commit
Some topics are now newly in 'next'.
* jk/test-seq-format (2025-06-23) 2 commits
* jt/imap-send-message-fix (2025-06-20) 3 commits
* jk/submodule-remote-lookup-cleanup (2025-06-23) 7 commits
* jc/merge-compact-summary (2025-06-12) 2 commits
* bc/stash-export-import (2025-06-11) 4 commits
* ps/contrib-sweep (2025-05-12) 11 commits
For details of each topic, please refer to its entry in the last
edition of the "What's cooking" report.
next prev parent reply other threads:[~2025-06-24 19:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 0:57 What's cooking in git.git (Jun 2025, #08; Mon, 23) Junio C Hamano
2025-06-24 19:01 ` Junio C Hamano [this message]
2025-06-24 23:29 ` Karthik Nayak
2025-06-25 15:03 ` Junio C Hamano
2025-06-25 8:40 ` Phillip Wood
2025-06-25 16:29 ` Junio C Hamano
2025-06-25 22:12 ` brian m. carlson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqqzz9yndx.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.