git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: git@vger.kernel.org
Cc: Jason Riedy <jason@acm.org>,
	Ramsay Jones <ramsay@ramsay1.demon.co.uk>,
	Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 0/2] fix NO_C99_FORMAT on 64-bit systems
Date: Wed, 16 Mar 2011 00:12:44 -0500	[thread overview]
Message-ID: <20110316051232.GA1932@elie> (raw)
In-Reply-To: <27484.1172021696@lotus.CS.Berkeley.EDU>

Hi,

Jason Riedy wrote:

> There are no direct
> C99 translations for other uses of NO_C99_FORMAT in git, alas.

So here's an indirect one. :)

The goal of this series is to unbreak "make CC=c89 NO_C99_FORMAT=yeah"
on my amd64 machine.  Side-effects include uglifying mktag a little
and eliminating the NO_C99_FORMAT knob.

Thoughts welcome, as always.

Jonathan Nieder (2):
  mktag: avoid %td in format string
  unbreak and eliminate NO_C99_FORMAT

 Makefile        |   14 --------------
 alloc.c         |   11 ++---------
 builtin/mktag.c |   48 ++++++++++++++++++++++--------------------------
 config.mak.in   |    1 -
 configure.ac    |   24 ------------------------
 sha1_file.c     |    9 ++-------
 6 files changed, 26 insertions(+), 81 deletions(-)

  reply	other threads:[~2011-03-16  5:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-21  1:34 [PATCH] Check for PRIuMAX rather than NO_C99_FORMAT in fast-import.c Jason Riedy
2011-03-16  5:12 ` Jonathan Nieder [this message]
2011-03-16  5:14   ` [PATCH 1/2] mktag: avoid %td in format string Jonathan Nieder
2011-03-20  6:03     ` Junio C Hamano
2011-03-16  5:15   ` [PATCH 2/2] unbreak and eliminate NO_C99_FORMAT Jonathan Nieder

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=20110316051232.GA1932@elie \
    --to=jrnieder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jason@acm.org \
    --cc=ramsay@ramsay1.demon.co.uk \
    /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).