All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Matheus Tavares Bernardino <matheus.bernardino@usp.br>
Cc: git <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Feb 2021, #03; Wed, 17)
Date: Thu, 18 Feb 2021 10:25:57 -0800	[thread overview]
Message-ID: <xmqqmtw1grm2.fsf@gitster.g> (raw)
In-Reply-To: <CAHd-oW4SxfAdJyDOdgqFsw2biUHHnU9wo78SLQMxs2VTeOar6Q@mail.gmail.com> (Matheus Tavares Bernardino's message of "Thu, 18 Feb 2021 00:19:59 -0300")

Matheus Tavares Bernardino <matheus.bernardino@usp.br> writes:

> Hi, Junio
>
> On Wed, Feb 17, 2021 at 11:13 PM Junio C Hamano <gitster@pobox.com> wrote:
>>
>> * mt/grep-sparse-checkout (2021-02-09) 1 commit
>>  - grep: honor sparse-checkout on working tree searches
>>
>>  "git grep" has been tweaked to be limited to the sparse checkout
>>  paths.
>>
>>  Break out and fast-track bugfix from the remainder of the topic.
>>  cf. <CABPp-BFkACtF6LHkFJNt9dTOmwfQbf8ZO=BTrPYwPSmbqc9+hg@mail.gmail.com>
>
> Perhaps is this description outdated? I see that you have already
> picked up the bugfix [1] which was broken out from the previous
> version.
>
> [1]: https://lore.kernel.org/git/5f3f7ac77039d41d1692ceae4b0c5df3bb45b74a.1612901326.git.matheus.bernardino@usp.br/

Indeed, what is queued and listed above is the updated one from Feb
9th.  Let's mark it for 'next'.

Thanks.

  reply	other threads:[~2021-02-18 18:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-18  2:11 What's cooking in git.git (Feb 2021, #03; Wed, 17) Junio C Hamano
2021-02-18  3:19 ` Matheus Tavares Bernardino
2021-02-18 18:25   ` Junio C Hamano [this message]
2021-02-18  6:44 ` Martin Ågren
2021-02-18 19:31   ` Junio C Hamano
2021-02-18 10:44 ` Charvi Mendiratta
2021-02-18 19:36   ` Junio C Hamano
2021-02-19  6:14     ` Charvi Mendiratta

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=xmqqmtw1grm2.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=matheus.bernardino@usp.br \
    /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.