Re: [Patch size_t V3 00/19] use size_t

2017-08-18 Thread Martin Koegler
On Thu, Aug 17, 2017 at 10:35:54PM +0200, Torsten Bögershausen wrote: > On Wed, Aug 16, 2017 at 10:16:12PM +0200, Martin Koegler wrote: > > From: Martin Koegler > > > > This patchset is for next [24db08a6e8fed761d3bace7f2d5997806e20b9f7]. > > I applied it succesfully,

Re: [Patch size_t V3 00/19] use size_t

2017-08-17 Thread Torsten Bögershausen
On Wed, Aug 16, 2017 at 10:16:12PM +0200, Martin Koegler wrote: > From: Martin Koegler > > This patchset is for next [24db08a6e8fed761d3bace7f2d5997806e20b9f7]. I applied it succesfully, and run the test suite on a 32 bit system. The Laptop reported one brekage in

Re: [Patch size_t V3 00/19] use size_t

2017-08-16 Thread Junio C Hamano
Martin Koegler writes: > From: Martin Koegler > > This patchset is for next [24db08a6e8fed761d3bace7f2d5997806e20b9f7]. > Its a complete collection of all patches. Some errors were fixed and > it sticks with off_t for length in (pack) files.

[Patch size_t V3 00/19] use size_t

2017-08-16 Thread Martin Koegler
From: Martin Koegler This patchset is for next [24db08a6e8fed761d3bace7f2d5997806e20b9f7]. Its a complete collection of all patches. Some errors were fixed and it sticks with off_t for length in (pack) files. Object sizes are handled as size_t. Martin Koegler (19):