> -Original Message-
> From: Torsten Bögershausen [mailto:tbo...@web.de]
> Sent: Friday, March 31, 2017 12:22 AM
> To: David Turner ; git@vger.kernel.org
> Subject: Re: [PATCH] http.postbuffer: make a size_t
>
>
>
> On 30/03/17 22:29, David Turner wrote:
>
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
---
cache.h | 1 +
config.c | 17 +
David Turner writes:
> 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
> ---
> cache.h | 1 +
> config.c | 17 +
> ht
To: David Turner
> Cc: git
> Subject: Re: [PATCH] http.postbuffer: make a size_t
>
> On Thu, Mar 30, 2017 at 1:29 PM, David Turner
> wrote:
> > Unfortunately, in order to push some large repos, the http postbuffer
> > must sometimes exceed two gigabytes. On a 64-bit sys
On Thu, Mar 30, 2017 at 1:29 PM, 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.
I'm slightly curious what server you are pushing to that needs the
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
---
cache.h | 1 +
config.c | 17 +
http.c | 2 +-
3 files changed, 19 inse
6 matches
Mail list logo