Re: 64-bit support.

. Spillner wrote: > Can you be more specific about the limitation you suspect you are hitting? > 32,768 is not the "max 32-bit value." > > >> On Nov 14, 2013, at 6:58, Лежанкин Иван wrote: >> >> Hi! >> >> Do you plan to implement the 64-bit

64-bit support.

Hi! Do you plan to implement the 64-bit support in git? - Right now I have a problems sometimes with a huge repo and renaming detection. If I merge more than 32768 files at once, then the renaming detection fails, because of limitation inside git. The limitation is put by max 32-bit value. I twea

Re: Error message: unable to open object pack directory: .git/objects/pack: Too many open files

I've tried your commit. No more error messages. Looking forward to the next git version. Thanks. On 13 November 2013 07:32, Duy Nguyen wrote: > On Wed, Nov 13, 2013 at 10:04 AM, Bryan Turner wrote: >>> but it's only available in v1.5.0-rc0 or rc1. Could you try that >>> version? >> >> I believe

Re: Error message: unable to open object pack directory: .git/objects/pack: Too many open files

o. I have disabled gc in the referenced repo - to prevent all local repos from breaking. May this be the cause of problem? On 12 November 2013 18:19, Duy Nguyen wrote: > On Tue, Nov 12, 2013 at 3:02 PM, Лежанкин Иван wrote: >> I get this error message every time I want to do a `git push`

Re: Error message: unable to open object pack directory: .git/objects/pack: Too many open files

1024 On 12 November 2013 13:34, Konstantin Khomoutov wrote: > On Tue, 12 Nov 2013 12:02:38 +0400 > Лежанкин Иван wrote: > >> I get this error message every time I want to do a `git push`. >> git version: 1.8.4.2 >> >> Is it a known issue? Do you need additional

Error message: unable to open object pack directory: .git/objects/pack: Too many open files

I get this error message every time I want to do a `git push`. git version: 1.8.4.2 Is it a known issue? Do you need additional info to investigate it? Ivan. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info

Re: Huge possible memory leak while cherry-picking.

ugust 2013 00:39, Felipe Contreras wrote: > On Fri, Aug 9, 2013 at 7:13 AM, Лежанкин Иван wrote: >> I have tried to cherry-pick a range of ~200 commits from one branch to >> another. And you can't imagine how I was surprised when the git >> process ate 8 Gb of RAM and d

Huge possible memory leak while cherry-picking.

Hi, I have tried to cherry-pick a range of ~200 commits from one branch to another. And you can't imagine how I was surprised when the git process ate 8 Gb of RAM and died - before cherry-picking was complete. I downloaded git sources from master and built it with gperftools support (-ltcmalloc).