From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Dec 2022, #06; Sun, 18)
Date: Mon, 19 Dec 2022 12:07:41 +0900 [thread overview]
Message-ID: <xmqqh6xsum4i.fsf@gitster.g> (raw)
In-Reply-To: <xmqqh6xtw4uw.fsf@gitster.g> (Junio C. Hamano's message of "Sun, 18 Dec 2022 16:25:27 +0900")
Among the ones marked as "Will merge to 'master'" in the most recent
issue of the "What's cooking" report, the following topics haven't
changed since they were cooking in 'next' before the tip of 'next'
was rewound:
rj/branch-copy-and-rename
rr/status-untracked-advice
aw/complete-case-insensitive
sx/pthread-error-check-fix
rs/diff-parseopts
jk/avoid-redef-system-functions
jk/avoid-redef-system-functions-2.30
rs/t3920-crlf-eating-grep-fix
js/t3920-shell-and-or-fix
jh/fsmonitor-darwin-modernize
ab/t4023-avoid-losing-exit-status-of-diff
ab/t7600-avoid-losing-exit-status-of-git
ab/t5314-avoid-losing-exit-status
jh/t7527-unflake-by-forcing-cookie
rs/plug-pattern-list-leak-in-lof
rs/t4205-do-not-exit-in-test-script
Hence, even though it has only been a few days since they were
merged back to 'next', I'll be merging them down to 'master'.
There may be other topics in the same state, which hopefully will
hit 'master' shortly.
Thanks.
next prev parent reply other threads:[~2022-12-19 3:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-18 7:25 What's cooking in git.git (Dec 2022, #06; Sun, 18) Junio C Hamano
2022-12-19 3:07 ` Junio C Hamano [this message]
2022-12-19 10:49 ` ds/omit-trailing-hash-in-index (was: What's cooking in git.git (Dec 2022, #06; Sun, 18)) Ævar Arnfjörð Bjarmason
2022-12-20 13:39 ` Derrick Stolee
2022-12-20 13:45 ` Ævar Arnfjörð Bjarmason
2022-12-20 22:56 ` What's cooking in git.git (Dec 2022, #06; Sun, 18) Johannes Schindelin
2022-12-21 12:45 ` Junio C Hamano
2022-12-23 7:34 ` Johannes Schindelin
2022-12-23 9:11 ` Junio C Hamano
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=xmqqh6xsum4i.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).