Re: What's cooking in git.git (Aug 2019, #04; Wed, 14)

From: Junio C Hamano <gitster@pobox.com>
Date: Aug 15, 2019, 16:56 UTC
Message-ID: <xmqqef1m4baf.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <CAPUEspjWbHC2md3kFu8O88275pYSzpFmu9kjHEn4_0_hjxZ8MA@mail.gmail.com>

Carlo Arenas <carenas@gmail.com> writes:

Show 16 quoted lines

> On Wed, Aug 14, 2019 at 4:58 PM Matheus Tavares Bernardino
> <matheus.bernardino@usp.br> wrote:
>>
>> On Wed, Aug 14, 2019 at 6:27 PM Junio C Hamano <gitster@pobox.com> wrote:
>> >
>> [...]
>> > * mt/grep-submodules-working-tree (2019-07-30) 1 commit
>> >   (merged to 'next' on 2019-08-02 at e1a46a195f)
>> >  + grep: fix worktree case in submodules
>>
>> There is a new version of this patch here[1], addressing the comments
>> you and Christian made.
>
> since it is already in next, would be better to submit a patch on top
> of the current topic instead (more details in
> Documentation/SubmittingPatches).

Thanks. Or we could just go the lazier route. A new stable release would happen within a day or two, and then in a week or so after that, the tip of 'next' gets rewound and rebuilt on top of it. We can discard the older copy and replace with the newer one when it happens.