From: Junio C Hamano <gitster@pobox.com>
To: Elijah Newren <newren@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Dec 2021, #03; Fri, 10)
Date: Mon, 13 Dec 2021 10:28:36 -0800 [thread overview]
Message-ID: <xmqqtufccqaz.fsf@gitster.g> (raw)
In-Reply-To: CABPp-BEpcmxyRVzC4afRTCdV1W=RQxfzUPESbR_pFGmvTXqTtg@mail.gmail.com
Elijah Newren <newren@gmail.com> writes:
>> * en/sparse-checkout-set (2021-12-08) 10 commits
> ...
>> Need to check the reroll.
>> cf. <pull.1151.v3.git.git.1639108573.gitgitgadget@gmail.com>
>> source: <pull.1151.v2.git.git.1638908410.gitgitgadget@gmail.com>
>
> I'm confused by the status here; en/sparse-checkout-set already
> represents v3, not v2, so you've already picked up the reroll. (v3 is
> the one containing both Stolee & Victoria's Reviewed-by.) I think
> that also means your cf. should be labeled as the source, yes?
And the old one needs to be dropped. I meant to do so after
checking the v3 myself but haven't got around to it when the report
was sent.
>> * es/test-chain-lint (2021-12-09) 19 commits
> ...
>>
>> Broken &&-chains in the test scripts have been corrected.
>>
>> Will merge to 'next'?
>
> Eric sent a reroll of just patch 2 with some working clarifications.
> It's a small thing, but I think it'd be great if that re-rolled patch
> could be picked up and inserted into the series. Other than that,
> yeah the series is good to merge down. (Peff and Fabian seemed to
> think so too.)
Pointers?
I know Eric said in
<CAPig+cR0eKhz+ncWb4v9dSY0A03P+K0+WT90J2cBKvLqT8DXrA@mail.gmail.com>
"I am a bit hesitant about spamming the list", but I do not know
what came after it.
... starts a browser and looks ...
OK. I found it at
https://lore.kernel.org/git/20211211095837.26387-1-sunshine@sunshineco.com/
Will take a look. Thanks.
next prev parent reply other threads:[~2021-12-13 18:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-11 2:52 What's cooking in git.git (Dec 2021, #03; Fri, 10) Junio C Hamano
2021-12-11 3:44 ` ns/batched-fsync and ns/remerge-diff Neeraj Singh
2021-12-11 6:38 ` Elijah Newren
2021-12-11 8:39 ` What's cooking in git.git (Dec 2021, #03; Fri, 10) Eric Sunshine
2021-12-13 19:08 ` Junio C Hamano
2021-12-11 10:49 ` Elijah Newren
2021-12-13 18:28 ` Junio C Hamano [this message]
2021-12-15 18:47 ` Junio C Hamano
2021-12-11 22:09 ` tb/midx-bitmap-corruption-fix Taylor Blau
2021-12-15 18:47 ` tb/midx-bitmap-corruption-fix Junio C Hamano
2021-12-12 18:37 ` ab/common-main-cleanup (was: What's cooking in git.git (Dec 2021, #03; Fri, 10)) Ævar Arnfjörð Bjarmason
2021-12-12 18:41 ` ab/only-single-progress-at-once " Ævar Arnfjörð Bjarmason
2021-12-13 4:44 ` ab/only-single-progress-at-once Junio C Hamano
2021-12-12 22:42 ` ms/customizable-ident-expansion (was: What's cooking in git.git (Dec 2021, #03; Fri, 10)) Ævar Arnfjörð Bjarmason
2021-12-13 9:02 ` ms/customizable-ident-expansion Junio C Hamano
2021-12-13 15:32 ` What's cooking in git.git (Dec 2021, #03; Fri, 10) Jeff Hostetler
2021-12-13 15:39 ` Jeff Hostetler
2021-12-14 10:59 ` 'Re: What's cooking in git.git (Dec 2021, #03; Fri, 10)' Teng Long
2021-12-15 18:53 ` Junio C Hamano
2021-12-15 11:10 ` What's cooking in git.git (Dec 2021, #03; Fri, 10) Phillip Wood
2021-12-15 18:54 ` 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=xmqqtufccqaz.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=newren@gmail.com \
/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).