From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Dec 2022, #05; Wed, 14)
Date: Fri, 16 Dec 2022 07:45:22 +0900 [thread overview]
Message-ID: <xmqq359gqoal.fsf@gitster.g> (raw)
In-Reply-To: <xmqqiliewbje.fsf@gitster.g> (Junio C. Hamano's message of "Wed, 14 Dec 2022 18:59:49 +0900")
Junio C Hamano <gitster@pobox.com> writes:
Let's mark the following to "Will merge to 'next'" again.
> * rs/t3920-crlf-eating-grep-fix (2022-12-07) 1 commit
> - t3920: support CR-eating grep
> (this branch uses js/t3920-shell-and-or-fix.)
>
> Test fix.
>
> Will merge back to 'next'.
> source: <cbe88abc-c1fb-cb50-6057-47ff27f7a12d@web.de>
With reviews by Philippe and Eric, this one still looks reasonable.
> * ab/t4023-avoid-losing-exit-status-of-diff (2022-12-05) 1 commit
> - t4023: fix ignored exit codes of git
>
> Test fix.
>
> Will merge back to 'next'.
> source: <patch-v2-3.8-c5feef1c808-20221202T000227Z-avarab@gmail.com>
Simple, obvious and trivially correct.
> * jh/t7527-unflake-by-forcing-cookie (2022-12-02) 1 commit
> - fsmonitor: fix race seen in t7527
>
> Make fsmonitor more robust to avoid the flakiness seen in t7527.
>
> Will merge back to 'next'.
> source: <pull.1437.git.1669937534944.gitgitgadget@gmail.com>
<xmqqfsdgqonk.fsf@gitster.g>.
> * rs/plug-pattern-list-leak-in-lof (2022-12-02) 1 commit
> - list-objects-filter: plug pattern_list leak
>
> Leak fix.
>
> Will merge back to 'next'.
> source: <b4361c3e-852b-e30c-f240-86c34bc9c474@web.de>
Simple, obvious and trivially correct.
> * rs/t4205-do-not-exit-in-test-script (2022-12-02) 1 commit
> - t4205: don't exit test script on failure
>
> Test fix.
>
> Will merge back to 'next'.
> source: <c5b4d091-23c1-5a75-a255-99ec83973d8d@web.de>
Ditto.
> * ab/t5314-avoid-losing-exit-status (2022-12-02) 1 commit
> - t5314: check exit code of "git"
>
> Test fix.
>
> Will merge back to 'next'.
> source: <patch-v2-1.1-ca77a7249e6-20221128T141818Z-avarab@gmail.com>
Ditto.
> * ab/t7600-avoid-losing-exit-status-of-git (2022-12-05) 1 commit
> - t7600: don't ignore "rev-parse" exit code in helper
>
> Test fix.
>
> Will merge back to 'next'.
> source: <patch-v3-1.8-64dfec31fb3-20221202T114733Z-avarab@gmail.com>
Ditto.
> * jh/fsmonitor-darwin-modernize (2022-12-05) 1 commit
> - fsmonitor: eliminate call to deprecated FSEventStream function
>
> Stop using deprecated macOS API in fsmonitor.
>
> Will merge back to 'next'.
> source: <pull.1436.git.1669991072393.gitgitgadget@gmail.com>
This one was updated <pull.1436.v2.git.1671045153981.gitgitgadget@gmail.com>
next prev parent reply other threads:[~2022-12-15 22:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 9:59 What's cooking in git.git (Dec 2022, #05; Wed, 14) Junio C Hamano
2022-12-14 10:44 ` Junio C Hamano
2022-12-14 19:46 ` Taylor Blau
2022-12-14 15:09 ` Derrick Stolee
2022-12-14 23:50 ` Junio C Hamano
2022-12-14 19:09 ` Jeff Hostetler
2022-12-14 23:50 ` Junio C Hamano
2022-12-14 19:18 ` Jeff Hostetler
2022-12-15 22:37 ` Junio C Hamano
2022-12-15 9:14 ` ag/merge-strategies-in-c (was: What's cooking in git.git (Dec 2022, #05; Wed, 14)) Ævar Arnfjörð Bjarmason
2022-12-15 12:55 ` Phillip Wood
2022-12-15 15:32 ` Ævar Arnfjörð Bjarmason
2022-12-15 16:27 ` Phillip Wood
2022-12-15 16:29 ` Ævar Arnfjörð Bjarmason
2022-12-15 9:33 ` ab/remove--super-prefix & ab/submodule-no-abspath " Ævar Arnfjörð Bjarmason
2022-12-15 9:49 ` js/bisect-in-c " Ævar Arnfjörð Bjarmason
2022-12-15 11:55 ` What's cooking in git.git (Dec 2022, #05; Wed, 14) Sean Allred
2022-12-15 22:45 ` Junio C Hamano [this message]
2022-12-15 23:09 ` Junio C Hamano
2022-12-16 15:33 ` ds/bundle-uri-4* (was Re: What's cooking in git.git (Dec 2022, #05; Wed, 14)) Derrick Stolee
2022-12-16 22:55 ` 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=xmqq359gqoal.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.