From: Ramkumar Ramachandra <artagnon@gmail.com>
To: David Barr <david.barr@cordelta.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Jonathan Nieder <jrnieder@gmail.com>,
Sverre Rabbelier <srabbelier@gmail.com>
Subject: Re: [PATCH] vcs-svn: Avoid %z in format string
Date: Sat, 4 Sep 2010 17:50:56 +0530 [thread overview]
Message-ID: <20100904122053.GC32397@kytes> (raw)
In-Reply-To: <1283601539-4477-1-git-send-email-david.barr@cordelta.com>
Hi David,
David Barr writes:
> In the spirit of v1.6.4-rc0~124 (MinGW: Fix compiler warning in
> merge-recursive, 2009-05-23), use a 64-bit integer instead.
Squashed. Thanks much :)
-- Ram
prev parent reply other threads:[~2010-09-04 12:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-04 7:43 [PATCH] Mockup an svndiff version 0 parser Ramkumar Ramachandra
2010-09-04 7:43 ` [WIP PATCH] vcs-svn: Add an svndiff0 parser Ramkumar Ramachandra
2010-09-04 11:58 ` [PATCH] vcs-svn: Avoid %z in format string David Barr
2010-09-04 12:20 ` Ramkumar Ramachandra [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=20100904122053.GC32397@kytes \
--to=artagnon@gmail.com \
--cc=david.barr@cordelta.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=srabbelier@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 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).