From: Johannes Sixt <j.sixt@viscovery.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Dec 2012, #04; Sun, 16)
Date: Tue, 18 Dec 2012 09:38:50 +0100 [thread overview]
Message-ID: <50D02B9A.1040906@viscovery.net> (raw)
In-Reply-To: <20121217213730.GA17212@ftbfs.org>
> Junio C Hamano wrote:
>> It could turn out that we may be able to get rid of sys/param.h
>> altogether, but one step at a time. Inputs from people on minority
>> platforms are very much appreciated---does your platform build fine
>> when the inclusion of the file is removed from git-compat-util.h?
MinGW works fine with sys/param.h removed from git-compat-util.h.
-- Hannes
next prev parent reply other threads:[~2012-12-18 8:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-17 21:37 What's cooking in git.git (Dec 2012, #04; Sun, 16) Matt Kraai
2012-12-18 8:28 ` Joachim Schmitz
2012-12-18 8:38 ` Johannes Sixt [this message]
2012-12-18 17:01 ` sys/param.h Junio C Hamano
2012-12-18 17:35 ` [RFH/PATCH] git-compat-util.h: do not #include <sys/param.h> by default Junio C Hamano
2012-12-18 19:46 ` sys/param.h Torsten Bögershausen
2012-12-19 7:59 ` sys/param.h Erik Faye-Lund
2012-12-20 2:49 ` sys/param.h Mark Levedahl
2012-12-20 3:03 ` sys/param.h Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2012-12-17 7:22 What's cooking in git.git (Dec 2012, #04; Sun, 16) 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50D02B9A.1040906@viscovery.net \
--to=j.sixt@viscovery.net \
--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).