From: Lars Schneider <larsxschneider@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, Eric Wong <e@80x24.org>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jul 2016, #05; Wed, 13)
Date: Sat, 16 Jul 2016 22:54:39 +0200 [thread overview]
Message-ID: <FB76544F-16F7-45CA-9649-FD62EE44B0DE@gmail.com> (raw)
In-Reply-To: <xmqqy4551nph.fsf@gitster.mtv.corp.google.com>
> On 13 Jul 2016, at 18:56, Junio C Hamano <gitster@pobox.com> wrote:
>
...
>
> * ew/http-walker (2016-07-12) 3 commits
> - http-walker: reduce O(n) ops with doubly-linked list
> - http: avoid disconnecting on 404s for loose objects
> - http-walker: remove unused parameter from fetch_object
>
> Optimize dumb http transport on the client side.
It looks like as if this topic breaks the OS X build because
it defines LIST_HEAD. LIST_HEAD is already defined in
/usr/include/sys/queue.h.
See: https://travis-ci.org/git/git/jobs/145121761
- Lars
next prev parent reply other threads:[~2016-07-16 20:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 16:56 What's cooking in git.git (Jul 2016, #05; Wed, 13) Junio C Hamano
2016-07-13 17:27 ` Stefan Beller
2016-07-13 17:32 ` Junio C Hamano
2016-07-13 17:52 ` Stefan Beller
2016-07-13 17:55 ` Junio C Hamano
2016-07-13 22:41 ` Junio C Hamano
2016-07-13 22:42 ` Jeff King
2016-07-13 17:40 ` Duy Nguyen
2016-07-13 17:46 ` Junio C Hamano
2016-07-14 12:59 ` Johannes Schindelin
2016-07-14 13:15 ` Johannes Schindelin
2016-07-14 15:45 ` Junio C Hamano
2016-07-14 13:46 ` Johannes Schindelin
2016-07-14 15:48 ` Junio C Hamano
2016-07-16 20:54 ` Lars Schneider [this message]
2016-07-16 21:04 ` Eric Wong
2016-07-16 22:04 ` Lars Schneider
2016-07-17 0:25 ` [PATCH] list: avoid incompatibility with *BSD sys/queue.h Eric Wong
2016-07-17 5:58 ` Eric Sunshine
2016-07-17 23:07 ` Eric Wong
2016-07-18 16:08 ` Lars Schneider
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=FB76544F-16F7-45CA-9649-FD62EE44B0DE@gmail.com \
--to=larsxschneider@gmail.com \
--cc=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).