From: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
To: dpmcgee@gmail.com
Cc: Junio C Hamano <gitster@pobox.com>,
GIT Mailing-list <git@vger.kernel.org>
Subject: [PATCH] builtin/pack-objects.c: Fix a printf format compiler warning
Date: Wed, 19 Oct 2011 20:10:37 +0100 [thread overview]
Message-ID: <4E9F20AD.4020209@ramsay1.demon.co.uk> (raw)
In particular, on systems that define uint32_t as an unsigned long,
gcc complains as follows:
CC builtin/pack-objects.o
pack-objects.c: In function `compute_write_order':
pack-objects.c:600: warning: unsigned int format, uint32_t arg (arg 3)
In order to suppress the warning, we use the C99 format specifier
macro PRIu32.
Signed-off-by: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
---
Hi Dan,
If you need to re-roll your pack-objects series (dm/pack-objects-update
branch in pu), could you please squash this change into your final commit
0a8145bd (pack-objects: don't traverse objects unnecessarily, 18-10-2011).
If you don't need to re-roll, then I'm hoping Junio will notice and squash
this in before it hits next. ;-)
ATB,
Ramsay Jones
builtin/pack-objects.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/builtin/pack-objects.c b/builtin/pack-objects.c
index 6db45fa..4bbd815 100644
--- a/builtin/pack-objects.c
+++ b/builtin/pack-objects.c
@@ -597,7 +597,7 @@ static struct object_entry **compute_write_order(void)
}
if (wo_end != nr_objects)
- die("ordered %u objects, expected %u", wo_end, nr_objects);
+ die("ordered %u objects, expected %"PRIu32, wo_end, nr_objects);
return wo;
}
--
1.7.7
next reply other threads:[~2011-10-20 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-19 19:10 Ramsay Jones [this message]
2011-10-20 18:54 ` [PATCH] builtin/pack-objects.c: Fix a printf format compiler warning Dan McGee
2011-10-21 0:17 ` Junio C Hamano
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=4E9F20AD.4020209@ramsay1.demon.co.uk \
--to=ramsay@ramsay1.demon.co.uk \
--cc=dpmcgee@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 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).