All of lore.kernel.org
 help / color / mirror / Atom feed
From: Charles Bailey <charles@hashpling.org>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Cc: Elia Pinto <gitter.spiros@gmail.com>
Subject: Re: [PATCH v2] Fix definition of ARRAY_SIZE for non-gcc builds
Date: Wed, 24 Jun 2015 23:19:10 +0100	[thread overview]
Message-ID: <20150624221910.GA21368@hashpling.org> (raw)
In-Reply-To: <1435183927-21217-1-git-send-email-charles@hashpling.org>

On Wed, Jun 24, 2015 at 11:12:07PM +0100, Charles Bailey wrote:
> From: Charles Bailey <cbailey32@bloomberg.net>
> 
> The improved ARRAY_SIZE macro uses BARF_UNLESS_AN_ARRAY which is expands
> to a valid check for recent gcc versions and to 0 for older gcc
> versions but is not defined on non-gcc builds.
 
Actually hitting send is a sure fire way to get me spot other errors:
s/which is expands/which expands/

      reply	other threads:[~2015-06-24 22:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-24  7:44 [PATCH] Fix definition of ARRAY_SIZE for non-gcc builds Charles Bailey
2015-06-24 22:12 ` [PATCH v2] " Charles Bailey
2015-06-24 22:19   ` Charles Bailey [this message]

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=20150624221910.GA21368@hashpling.org \
    --to=charles@hashpling.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=gitter.spiros@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.