From: Junio C Hamano <gitster@pobox.com>
To: Carlo Arenas <carenas@gmail.com>
Cc: Matheus Tavares Bernardino <matheus.bernardino@usp.br>,
git <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Aug 2019, #04; Wed, 14)
Date: Thu, 15 Aug 2019 09:56:56 -0700 [thread overview]
Message-ID: <xmqqef1m4baf.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CAPUEspjWbHC2md3kFu8O88275pYSzpFmu9kjHEn4_0_hjxZ8MA@mail.gmail.com> (Carlo Arenas's message of "Wed, 14 Aug 2019 19:15:50 -0700")
Carlo Arenas <carenas@gmail.com> writes:
> 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.
next prev parent reply other threads:[~2019-08-15 16:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 21:27 What's cooking in git.git (Aug 2019, #04; Wed, 14) Junio C Hamano
2019-08-14 23:18 ` Matheus Tavares Bernardino
2019-08-15 2:15 ` Carlo Arenas
2019-08-15 16:56 ` Junio C Hamano [this message]
2019-08-16 0:30 ` Matheus Tavares Bernardino
2019-08-16 16:42 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqef1m4baf.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=carenas@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).