From: Junio C Hamano <gitster@pobox.com>
To: Thomas Gummerer <t.gummerer@gmail.com>
Cc: Kevin Willford <kewillf@microsoft.com>,
"git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Sep 2017, #02; Mon, 11)
Date: Tue, 12 Sep 2017 11:16:32 +0900 [thread overview]
Message-ID: <xmqqd16w3blr.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20170911195340.GB26081@hank> (Thomas Gummerer's message of "Mon, 11 Sep 2017 20:53:40 +0100")
Thomas Gummerer <t.gummerer@gmail.com> writes:
> On 09/11, Kevin Willford wrote:
>> >
>> > * kw/write-index-reduce-alloc (2017-09-08) 2 commits
>> > - read-cache: fix index corruption with index v4
>> > - Add t/helper/test-write-cache to .gitignore
>> >
>> > Expecting a reroll.
>> > cf. <CALgYhfNYgmCJqptNQLKaQpCs9mAgqZHUrDS3BVEqCv_f+WX-
>> > qg@mail.gmail.com>
>> >
>> I didn't submit these patches so what would you like
>> me to do?
Nothing ;-).
These two are fixups to a recent topic; the name of the topic branch
does not mean fixes and updates must come only from those who share
the initial 'kw'.
>> The reroll for read-cache fix was submitted here
>> https://public-inbox.org/git/20170907192412.8085-1-t.gummerer@gmail.com/
>
> I noticed that it has already been picked up as well, as
> 0b90b881e0c1de110c724fe63df6d2c3c9680d6a. Maybe it's just the What's
> cooking that needs to be updated, or is there something else missing?
Yeah, thanks for keeping an eye on what's on 'pu'.
next prev parent reply other threads:[~2017-09-12 2:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 1:38 What's cooking in git.git (Sep 2017, #02; Mon, 11) Junio C Hamano
2017-09-11 19:26 ` Kevin Willford
2017-09-11 19:53 ` Thomas Gummerer
2017-09-12 2:16 ` Junio C Hamano [this message]
2017-09-12 11:30 ` Johannes Schindelin
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=xmqqd16w3blr.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=kewillf@microsoft.com \
--cc=t.gummerer@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).