From: Avery Pennarun <apenwarr@gmail.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: "Gary V. Vaughan" <git@mlists.thewrittenword.com>, git@vger.kernel.org
Subject: Re: [patch 02/15] const-expr.patch
Date: Tue, 16 Mar 2010 19:43:54 -0400 [thread overview]
Message-ID: <32541b131003161643g1a1cbf6ck3089ae5fb016a985@mail.gmail.com> (raw)
In-Reply-To: <4B9F33DC.3030309@viscovery.net>
On Tue, Mar 16, 2010 at 3:31 AM, Johannes Sixt <j.sixt@viscovery.net> wrote:
> Gary V. Vaughan schrieb:
>> Unfortunately, there are still plenty of production systems with
>> vendor compilers that choke unless all compound declarations can be
>> determined statically at compile time, for example hpux10.20 (I can
>> provide a comprehensive list of our supported platforms that exhibit
>> this problem if necessary).
>
> Yes, a comprehensive list would be appreciated. This change is an
> uglification that I personally would prefer to stay out of the code base
> unless many consumers of git are hurt.
>
> The problem with this non-feature is that it is all too easy that new code
> introduces new incompatibilities.
This is probably a stupid question, but why not just build it using
gcc on systems with a broken vendor compiler? You don't have to
distribute gcc just to distribute binaries built with it, so it seems
like there's no downside... and less suffering for the build
maintainer.
Have fun,
Avery
next prev parent reply other threads:[~2010-03-16 23:50 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 5:42 [patch 00/15] Portability Patches v3 Gary V. Vaughan
2010-03-16 5:42 ` [patch 01/15] user-cppflags.patch Gary V. Vaughan
2010-03-16 7:21 ` Junio C Hamano
2010-03-16 5:42 ` [patch 02/15] const-expr.patch Gary V. Vaughan
2010-03-16 7:31 ` Johannes Sixt
2010-03-16 8:23 ` Gary V. Vaughan
2010-03-16 23:43 ` Avery Pennarun [this message]
2010-04-25 8:38 ` Gary V. Vaughan
2010-03-16 5:42 ` [patch 03/15] pthread.patch Gary V. Vaughan
2010-03-16 7:21 ` Junio C Hamano
2010-03-16 5:42 ` [patch 04/15] diff-export.patch Gary V. Vaughan
2010-03-16 7:24 ` Junio C Hamano
2010-03-16 5:42 ` [patch 05/15] diff-test_cmp.patch Gary V. Vaughan
2010-03-16 7:21 ` Junio C Hamano
2010-04-25 8:38 ` Gary V. Vaughan
2010-03-16 5:42 ` [patch 06/15] diff-defaults.patch Gary V. Vaughan
2010-03-16 7:22 ` Junio C Hamano
2010-04-25 8:38 ` Gary V. Vaughan
2010-03-16 5:42 ` [patch 07/15] host-IRIX.patch Gary V. Vaughan
2010-03-16 7:24 ` Junio C Hamano
2010-04-25 8:39 ` Gary V. Vaughan
2010-03-16 15:27 ` Brandon Casey
2010-04-25 8:39 ` Gary V. Vaughan
2010-03-16 5:42 ` [patch 08/15] host-HPUX10.patch Gary V. Vaughan
2010-03-16 5:42 ` [patch 09/15] host-HPUX11.patch Gary V. Vaughan
2010-03-16 5:42 ` [patch 10/15] host-OSF1.patch Gary V. Vaughan
2010-03-16 5:42 ` [patch 11/15] no-hstrerror.patch Gary V. Vaughan
2010-03-16 7:24 ` Junio C Hamano
2010-04-25 8:39 ` Gary V. Vaughan
2010-03-16 5:42 ` [patch 12/15] no-inet_ntop.patch Gary V. Vaughan
2010-03-16 5:42 ` [patch 13/15] no-socklen_t.patch Gary V. Vaughan
2010-03-16 7:25 ` Junio C Hamano
2010-04-25 8:39 ` Gary V. Vaughan
2010-03-16 5:42 ` [patch 14/15] no-ss_family.patch Gary V. Vaughan
2010-03-16 5:42 ` [patch 15/15] no-inline.patch Gary V. Vaughan
2010-03-16 6:18 ` [patch 00/15] Portability Patches v3 Sverre Rabbelier
2010-03-16 16:03 ` Brandon Casey
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=32541b131003161643g1a1cbf6ck3089ae5fb016a985@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=git@mlists.thewrittenword.com \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.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 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).