GfW is an abbreviation for Git for Windows' - I think I'd introduced it
earlier in one of the posts.
The "Native" size for Windows, in backwards compatibility terms (which
is at the "compiled binary" level") is 32 bits, i.e. old code runs
without change. Hence the addition of "long long" by
On Thursday, March 3, 2022 at 3:54:25 PM UTC+1 philip...@iee.email wrote:
> > Am I correct in that the work to make mainline Git use size_t where
> applicable
> is ongoing?
>
> It's currently a little stalled, because it's been hard to partition the
> problem into small chunks that fit
On Thursday, March 3, 2022 at 11:42:54 AM UTC+1 Konstantin Khomoutov wrote:
> On Wed, Mar 02, 2022 at 06:03:46PM +, Skybuck Flying wrote:
>
> >> Search for "4GB" in this blog post [1] which discusses the GfW 2.35
> release
> >> notes.
> >>
> >> 1.
> Am I correct in that the work to make mainline Git use size_t where
applicable
is ongoing?
It's currently a little stalled, because it's been hard to partition the
problem into small chunks that fit everyone's expectations about what
should be in or out for tidying up consequences (e.g.
On Thu, Mar 03, 2022 at 03:03:34AM -0800, Philip Oakley wrote:
>> By the way, do you use a 64-bit install? If, for some reason, you're using
>> a 32-bit version, the limit of circa 4 GB (actaually lower) will be
>> "native".
>
> The Git code is merely POSIX compliant (long == size_t; LP64),
> By the way, do you use a 64-bit install? If, for some reason, you're
using a
32-bit version, the limit of circa 4 GB (actaually lower) will be "native".
The Git code is merely POSIX compliant (long == size_t; LP64), while Git
for Windows uses LLP64 (long=32bits; long long == size_t).
Vast
On Wed, Mar 02, 2022 at 06:03:46PM +, Skybuck Flying wrote:
>> Search for "4GB" in this blog post [1] which discusses the GfW 2.35 release
>> notes.
>>
>> 1. https://github.blog/2022-01-24-highlights-from-git-2-35/
> Thanks for the update, however I don't see how this could effect git
>
Hi,
My latest hypothesis what might have happened during that normal git
checkout on linux kernel is that there was some kind of memory
fragmentation and windows could not return enough memory.
Test programs could be written to test this hypothesis but I have no time
for this.
Bye,
Skybuck, maybe this will help clear up this issue:
https://www.helpndoc.com/documentation/html/Windowsreservedfilenames.html
Saga
-Original Message-
From: skybuck2000
To: Git for human beings
Sent: Mon, Feb 28, 2022 12:47 am
Subject: [git-users] Re: GIT failed to checkout the linux
On Wed, Dec 01, 2021 at 09:32:56PM -0800, skybuck2000 wrote:
> It would be nice if GIT would respect the following limits:
>
> new@new-PC MINGW64 /
> $ ulimit -a
> core file size (blocks, -c) unlimited
> data seg size (kbytes, -d) unlimited
> file size (blocks,
10 matches
Mail list logo
