From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Michael Blume <blume.mike@gmail.com>,
"brian m. carlson" <sandals@crustytoothpaste.net>,
Git List <git@vger.kernel.org>, Duy Nguyen <pclouds@gmail.com>
Subject: Re: [PATCH v3 2/4] rev-list: add an option to mark fewer edges as uninteresting
Date: Tue, 23 Dec 2014 11:11:32 -0800 [thread overview]
Message-ID: <xmqqvbl218rf.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20141223185142.GA27954@peff.net> (Jeff King's message of "Tue, 23 Dec 2014 13:51:42 -0500")
Jeff King <peff@peff.net> writes:
> On Tue, Dec 23, 2014 at 12:55:48PM -0500, Michael Blume wrote:
>
>> This patch causes an error on my mac, test 5500 fetch-pack errors on
>> part 44 - fetch creating new shallow root. It looks for "remote: Total
>> 1" in the fetch output and gets 3 instead.
>
> It fails for me on Linux, too. Interestingly the tip of the series
> passes. I didn't investigate further.
Not surprised, as the first three are the same from the yesterday's
one that failed for everybody.
next prev parent reply other threads:[~2014-12-23 19:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-23 12:01 [PATCH v3 0/4] Improve push performance with lots of refs brian m. carlson
2014-12-23 12:01 ` [PATCH v3 1/4] Documentation: add missing article in rev-list-options.txt brian m. carlson
2014-12-23 12:01 ` [PATCH v3 2/4] rev-list: add an option to mark fewer edges as uninteresting brian m. carlson
2014-12-23 17:55 ` Michael Blume
2014-12-23 18:51 ` Jeff King
2014-12-23 19:11 ` Junio C Hamano [this message]
2014-12-24 21:26 ` brian m. carlson
2014-12-23 12:01 ` [PATCH v3 3/4] pack-objects: use --objects-edge-aggressive only for shallow repos brian m. carlson
2014-12-23 12:01 ` [PATCH v3 4/4] upload-pack: use --objects-edge-aggressive for shallow fetches brian m. carlson
2014-12-23 18:40 ` [PATCH v3 0/4] Improve push performance with lots of refs Junio C Hamano
2014-12-24 21:31 ` brian m. carlson
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=xmqqvbl218rf.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=blume.mike@gmail.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
/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.