git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sverre Rabbelier <srabbelier@gmail.com>
To: "Gary V. Vaughan" <git@mlists.thewrittenword.com>
Cc: git@vger.kernel.org
Subject: Re: [patch 00/15] Portability Patches v3
Date: Tue, 16 Mar 2010 07:18:48 +0100	[thread overview]
Message-ID: <fabb9a1e1003152318m204f178cpbe9eb82cb2742586@mail.gmail.com> (raw)
In-Reply-To: <20100316054220.075676000@mlists.thewrittenword.com>

Heya,

On Tue, Mar 16, 2010 at 06:42, Gary V. Vaughan
<git@mlists.thewrittenword.com> wrote:
> Here are the portability patches we needed at TWW to enable
> git-1.7.0.2 to compile and run on all of the wide range of Unix
> machines we support.

Oh wow, thanks! Glad to see you followed up on this, awesome!

> Note that I have not invested the time to figure out why the testsuite
> is mostly useless on everything but Linux and Solaris 8+, because I'm
> reasonably satisfied that the build itself is working properly.

I'm curious now, what kind of errors are you getting? Would you mind
perhaps posting a few to the list in a new thread?

-- 
Cheers,

Sverre Rabbelier

  parent reply	other threads:[~2010-03-16  6:19 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
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 ` Sverre Rabbelier [this message]
2010-03-16 16:03 ` [patch 00/15] Portability Patches v3 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=fabb9a1e1003152318m204f178cpbe9eb82cb2742586@mail.gmail.com \
    --to=srabbelier@gmail.com \
    --cc=git@mlists.thewrittenword.com \
    --cc=git@vger.kernel.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).