From: Jeff King <peff@peff.net>
To: "Gary V. Vaughan" <git@mlists.thewrittenword.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
Michael J Gruber <git@drmicha.warpmail.net>,
git@vger.kernel.org
Subject: Re: [patch 00/16] Portability Patches for git-1.7.1 (v4)
Date: Wed, 28 Apr 2010 08:17:56 -0400 [thread overview]
Message-ID: <20100428121756.GA17244@sigill.intra.peff.net> (raw)
In-Reply-To: <20100428091922.GF36271@thor.il.thewrittenword.com>
On Wed, Apr 28, 2010 at 09:19:22AM +0000, Gary V. Vaughan wrote:
> > > > Furthermore, if we do take such changes, how are we going to manage
> > > > portability going forward? Some constructs (like non-constant
> > > > initializers) make the code much easier to read. People _will_ submit
> > > > patches that use them. Is somebody going to be auto-building on all of
> > > > these platforms with vendor compilers to confirm that nothing is broken?
>
> And that's fine. People who are trying to build will notice the
> breakage on their platforms and likely submit patches in due course.
That was sort of implicit in my questions. _Is_ there somebody who is
going to be building on these platforms that will notice the breakage?
But it sounds from the rest of your mail like you are willing to do so,
which is at least encouraging.
-Peff
next prev parent reply other threads:[~2010-04-28 12:18 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 13:57 [patch 00/16] Portability Patches for git-1.7.1 (v4) Gary V. Vaughan
2010-04-27 13:57 ` [patch 01/16] user-cppflags.patch Gary V. Vaughan
2010-04-27 13:57 ` [patch 02/16] const-expr.patch Gary V. Vaughan
2010-04-27 14:08 ` Erik Faye-Lund
2010-04-27 14:32 ` Gary V. Vaughan
[not found] ` <1AFA5FB2-EB8B-4775-8941-86428C7F740E@gmail.com>
2010-05-03 1:39 ` Gary V. Vaughan
[not found] ` <A4E8B513-AD31-4F3B-9DEF-6A85AA8DC7B3@gmail.com>
2010-05-04 5:01 ` Gary V. Vaughan
2010-04-27 13:57 ` [patch 03/16] pthread.patch Gary V. Vaughan
2010-04-27 13:57 ` [patch 04/16] Without this patch at least IBM VisualAge C 5.0 (I have 5.0.2) on AIX 5.1 fails to compile git Gary V. Vaughan
2010-04-27 16:08 ` Tor Arntsen
2010-04-28 8:40 ` Gary V. Vaughan
2010-04-28 8:55 ` Tor Arntsen
2010-04-28 16:23 ` Jeff King
2010-04-27 13:57 ` [patch 05/16] diff-export.patch Gary V. Vaughan
2010-04-27 13:57 ` [patch 06/16] diff-test_cmp.patch Gary V. Vaughan
2010-04-27 17:15 ` Jonathan Nieder
2010-04-28 9:00 ` Gary V. Vaughan
2010-04-28 9:51 ` Jonathan Nieder
2010-04-28 10:22 ` Gary V. Vaughan
2010-04-28 17:43 ` Jonathan Nieder
2010-04-27 13:57 ` [patch 07/16] diff-defaults.patch Gary V. Vaughan
2010-04-27 13:57 ` [patch 08/16] host-SunOS56.patch Gary V. Vaughan
2010-04-27 13:57 ` [patch 09/16] host-IRIX.patch Gary V. Vaughan
2010-04-27 13:57 ` [patch 10/16] host-HPUX10.patch Gary V. Vaughan
2010-04-27 13:57 ` [patch 11/16] host-HPUX11.patch Gary V. Vaughan
2010-04-27 13:57 ` [patch 12/16] host-OSF1.patch Gary V. Vaughan
2010-04-27 14:10 ` Tor Arntsen
2010-04-27 14:39 ` Gary V. Vaughan
2010-04-27 14:48 ` Tor Arntsen
2010-04-28 9:07 ` Gary V. Vaughan
2010-04-27 13:57 ` [patch 13/16] no-hstrerror.patch Gary V. Vaughan
2010-04-27 13:57 ` [patch 14/16] no-inet_ntop.patch Gary V. Vaughan
2010-04-27 13:57 ` [patch 15/16] no-socklen_t.patch Gary V. Vaughan
2010-04-27 13:57 ` [patch 16/16] no-inline.patch Gary V. Vaughan
2010-04-27 15:30 ` [patch 00/16] Portability Patches for git-1.7.1 (v4) Michael J Gruber
2010-04-27 17:54 ` Jeff King
2010-04-27 20:13 ` Andreas Schwab
2010-04-28 2:08 ` Jeff King
2010-04-28 9:19 ` Gary V. Vaughan
2010-04-28 12:17 ` Jeff King [this message]
2010-04-28 9:27 ` Gary V. Vaughan
2010-04-28 9:32 ` Gary V. Vaughan
2010-04-28 12:26 ` Ævar Arnfjörð Bjarmason
[not found] ` <4BD94599.5090309@drmicha.warpmail.net>
2010-04-29 10:50 ` Gary V. Vaughan
2010-05-01 18:34 ` Michael J Gruber
2010-05-01 23:25 ` Junio C Hamano
2010-05-03 1:48 ` Gary V. Vaughan
2010-05-02 13:00 ` Øyvind A. Holm
2010-04-28 10:12 ` Gary V. Vaughan
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=20100428121756.GA17244@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@drmicha.warpmail.net \
--cc=git@mlists.thewrittenword.com \
--cc=git@vger.kernel.org \
--cc=schwab@linux-m68k.org \
/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).