From: Junio C Hamano <gitster@pobox.com>
To: Derrick Stolee <stolee@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: ds/commit-graph-incremental (was Re: What's cooking in git.git (Jun 2019, #04; Fri, 14))
Date: Wed, 19 Jun 2019 07:32:08 -0700 [thread overview]
Message-ID: <xmqqo92tr6hj.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <8690d49e-31f5-e12a-ae8c-dc217a5476cc@gmail.com> (Derrick Stolee's message of "Tue, 18 Jun 2019 09:36:08 -0400")
Derrick Stolee <stolee@gmail.com> writes:
> On 6/14/2019 4:50 PM, Junio C Hamano wrote:
>> * ds/commit-graph-incremental (2019-06-12) 16 commits
>> - commit-graph: test --split across alternate without --split
>
> Please hold on this one. I've found multiple issues while integrating
> this with VFS for Git and there are enough to merit a full re-roll.
Thanks.
> Please ignore the two patches I sent yesterday as I will incorporate them
> into the next version of this series.
I think I picked up "normalize c-g filenames" and queued it directly
on top of this topic, but I do not recall the other one, which
probably means I did ignore it so hopefully no harm done ;-)
next prev parent reply other threads:[~2019-06-19 14:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 20:50 What's cooking in git.git (Jun 2019, #04; Fri, 14) Junio C Hamano
2019-06-17 17:41 ` js/gcc-8-and-9, was " Johannes Schindelin
2019-06-17 19:54 ` Junio C Hamano
2019-06-18 10:26 ` Johannes Schindelin
2019-06-19 14:28 ` Junio C Hamano
2019-06-17 18:06 ` pw/rebase-abort-clean-rewritten, " Johannes Schindelin
2019-06-17 19:04 ` Phillip Wood
2019-06-18 3:30 ` Junio C Hamano
2019-06-20 9:34 ` Phillip Wood
2019-06-21 13:27 ` Johannes Schindelin
2019-06-17 18:25 ` sg/rebase-progress, " Johannes Schindelin
2019-06-18 13:36 ` ds/commit-graph-incremental (was Re: What's cooking in git.git (Jun 2019, #04; Fri, 14)) Derrick Stolee
2019-06-19 14:32 ` Junio C Hamano [this message]
2019-06-19 14:37 ` Derrick Stolee
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=xmqqo92tr6hj.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=stolee@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.
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).