From: "Torsten Bögershausen" <tboegi@web.de>
To: David Turner <dturner@twosigma.com>, git@vger.kernel.org
Subject: Re: [PATCH] http.postbuffer: make a size_t
Date: Fri, 31 Mar 2017 06:22:13 +0200 [thread overview]
Message-ID: <d312abfe-f87d-3940-ecfa-348fed7ad3a1@web.de> (raw)
In-Reply-To: <20170330202917.24281-1-dturner@twosigma.com>
On 30/03/17 22:29, David Turner wrote:
> Unfortunately, in order to push some large repos, the http postbuffer
> must sometimes exceed two gigabytes. On a 64-bit system, this is OK:
> we just malloc a larger buffer.
>
> Signed-off-by: David Turner <dturner@twosigma.com>
> ---
> cache.h | 1 +
> config.c | 17 +++++++++++++++++
> http.c | 2 +-
> 3 files changed, 19 insertions(+), 1 deletion(-)
>
> diff --git a/cache.h b/cache.h
> index fbdf7a815a..a8c1b65db0 100644
> --- a/cache.h
> +++ b/cache.h
> @@ -1900,6 +1900,7 @@ extern int git_parse_maybe_bool(const char *);
> extern int git_config_int(const char *, const char *);
> extern int64_t git_config_int64(const char *, const char *);
> extern unsigned long git_config_ulong(const char *, const char *);
> +extern size_t git_config_size_t(const char *, const char *);
> extern int git_config_bool_or_int(const char *, const char *, int *);
> extern int git_config_bool(const char *, const char *);
> extern int git_config_maybe_bool(const char *, const char *);
> diff --git a/config.c b/config.c
> index 1a4d85537b..7b706cf27a 100644
> --- a/config.c
> +++ b/config.c
> @@ -834,6 +834,15 @@ int git_parse_ulong(const char *value, unsigned long *ret)
> return 1;
> }
>
> +static size_t git_parse_size_t(const char *value, unsigned long *ret)
> +{
> + size_t tmp;
> + if (!git_parse_signed(value, &tmp, maximum_unsigned_value_of_type(size_t)))
> + return 0;
> + *ret = tmp;
> + return 1;
> +}
What is the return value here ?
Isn't it a size_t we want ?
(There was a recent discussion about "unsigned long" vs "size_t", which
are the same on many systems, but not under Win64)
Would the following work ?
static int git_parse_size_t(const char *value, size_t *ret)
{
if (!git_parse_signed(value, ret, maximum_unsigned_value_of_type(size_t)))
return 0;
return 1;
}
[]
> +size_t git_config_size_t(const char *name, const char *value)
> +{
> + unsigned long ret;
> + if (!git_parse_size_t(value, &ret))
> + die_bad_number(name, value);
> + return ret;
> +}
> +
Same here:
size_t git_config_size_t(const char *name, const char *value)
{
size_t ret;
if (!git_parse_size_t(value, &ret))
die_bad_number(name, value);
return ret;
}
next prev parent reply other threads:[~2017-03-31 4:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 20:29 [PATCH] http.postbuffer: make a size_t David Turner
2017-03-30 20:42 ` Shawn Pearce
2017-03-30 20:59 ` David Turner
2017-03-30 22:07 ` Junio C Hamano
2017-03-31 4:22 ` Torsten Bögershausen [this message]
2017-03-31 15:52 ` David Turner
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=d312abfe-f87d-3940-ecfa-348fed7ad3a1@web.de \
--to=tboegi@web.de \
--cc=dturner@twosigma.com \
--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).