From: Jason Riedy <ejr@cs.berkeley.edu>
To: "Simon 'corecode' Schubert" <corecode@fs.ei.tum.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Obey NO_C99_FORMAT in fast-import.c.
Date: Tue, 20 Feb 2007 12:17:50 -0800 [thread overview]
Message-ID: <19963.1172002670@lotus.CS.Berkeley.EDU> (raw)
In-Reply-To: 45DAF02C.4020003@fs.ei.tum.de
And Simon 'corecode' Schubert writes:
> I think this should read something like
>
> #ifndef PRIuMAX
> #define PRIuMAX "llu" /* Assumes unsigned long long exists */
> #endif
You're right, that's much cleaner. I'll try it and test it.
(Takes many hours to run a test on this poor machine, so the
patch won't be sent until tomorrow.)
Jason
next reply other threads:[~2007-02-20 20:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 20:17 Jason Riedy [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-20 0:27 [PATCH] Obey NO_C99_FORMAT in fast-import.c Jason Riedy
2007-02-20 12:57 ` Simon 'corecode' Schubert
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=19963.1172002670@lotus.CS.Berkeley.EDU \
--to=ejr@cs.berkeley.edu \
--cc=corecode@fs.ei.tum.de \
--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).