* [PATCH] builtin/pack-objects.c: Fix a printf format compiler warning
@ 2011-10-19 19:10 Ramsay Jones
2011-10-20 18:54 ` Dan McGee
2011-10-21 0:17 ` Junio C Hamano
0 siblings, 2 replies; 3+ messages in thread
From: Ramsay Jones @ 2011-10-19 19:10 UTC (permalink / raw)
To: dpmcgee; +Cc: Junio C Hamano, GIT Mailing-list
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
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH] builtin/pack-objects.c: Fix a printf format compiler warning
2011-10-19 19:10 [PATCH] builtin/pack-objects.c: Fix a printf format compiler warning Ramsay Jones
@ 2011-10-20 18:54 ` Dan McGee
2011-10-21 0:17 ` Junio C Hamano
1 sibling, 0 replies; 3+ messages in thread
From: Dan McGee @ 2011-10-20 18:54 UTC (permalink / raw)
To: Ramsay Jones; +Cc: Junio C Hamano, GIT Mailing-list
On Wed, Oct 19, 2011 at 2:10 PM, Ramsay Jones
<ramsay@ramsay1.demon.co.uk> wrote:
>
> 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. ;-)
Sorry about that- fixed locally, and if I do need to resend them then
it will be fixed.
-Dan
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] builtin/pack-objects.c: Fix a printf format compiler warning
2011-10-19 19:10 [PATCH] builtin/pack-objects.c: Fix a printf format compiler warning Ramsay Jones
2011-10-20 18:54 ` Dan McGee
@ 2011-10-21 0:17 ` Junio C Hamano
1 sibling, 0 replies; 3+ messages in thread
From: Junio C Hamano @ 2011-10-21 0:17 UTC (permalink / raw)
To: Ramsay Jones; +Cc: dpmcgee, Junio C Hamano, GIT Mailing-list
Ramsay Jones <ramsay@ramsay1.demon.co.uk> writes:
> If you don't need to re-roll, then I'm hoping Junio will notice and squash
> this in before it hits next. ;-)
Will do; thanks, both.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2011-10-21 0:17 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-10-19 19:10 [PATCH] builtin/pack-objects.c: Fix a printf format compiler warning Ramsay Jones
2011-10-20 18:54 ` Dan McGee
2011-10-21 0:17 ` Junio C Hamano
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).