All of lore.kernel.org
 help / color / mirror / Atom feed
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: Wed, 15 Dec 2021 10:47:31 -0800	[thread overview]
Message-ID: <xmqqr1ad7lj0.fsf@gitster.g> (raw)
In-Reply-To: <CABPp-BEpcmxyRVzC4afRTCdV1W=RQxfzUPESbR_pFGmvTXqTtg@mail.gmail.com> (Elijah Newren's message of "Sat, 11 Dec 2021 02:49:31 -0800")

Elijah Newren <newren@gmail.com> writes:

>> * ds/fetch-pull-with-sparse-index (2021-12-08) 6 commits
> ...
>>  Ejected from 'seen', as it seems to fail its self-test.
>>  source: <pull.1080.v2.git.1638992395.gitgitgadget@gmail.com>
>
> I _think_ Stolee addressed this in his v3 cover letter with his
> comment that he also needed to merge with master[1].  

The topic is built on a merge of "ld/sparse-diff-blame" into "master",
so "also needed to merge with master" should be satisified already.

>> * pw/diff-color-moved-fix (2021-12-09) 15 commits
> ...
>>  Will merge to 'next'?
>>  source: <pull.981.v5.git.1639045809.gitgitgadget@gmail.com>
>
> Dscho seemed to suggest that course of action[2].  (I also looked at
> the series, though much more lightly -- I couldn't spot any problems.)
>
> [2] https://lore.kernel.org/git/nycvar.QRO.7.76.6.2112081329030.90@tvgsbejvaqbjf.bet/.

Yup, after giving it another look, I agree that this is ready.

Thanks.

  parent reply	other threads:[~2021-12-15 18:47 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
2021-12-15 18:47   ` Junio C Hamano [this message]
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=xmqqr1ad7lj0.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 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.