Re: 64-bit support.

From: Konstantin Khomoutov <flatworm@users.sourceforge.net>
Date: Nov 14, 2013, 13:07 UTC
Message-ID: <20131114170719.646d77f0c656a0e752626c2d@domain007.com>
In-Reply-To: <CAJc7Lbr9Ej8JHo6m4HFwdo9GE2tBQCkypEMxMW+jEXKB1Lry=g@mail.gmail.com>

On Thu, 14 Nov 2013 16:58:31 +0400 Лежанкин Иван <abyss.7@gmail.com> wrote:

Show 9 quoted lines

> 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 tweaked sources locally, to use 64-bit value as a number of merging
> files - generally, it works. But I'm not so brave to try to replace it
> everywhere in git.

$ apt-cache policy git
git:
  Installed: 1:1.7.10.4-1+wheezy1
  Candidate: 1:1.7.10.4-1+wheezy1
  Version table:
 *** 1:1.7.10.4-1+wheezy1 0
        500 http://cdn.debian.net/debian/ wheezy/main amd64 Packages
        100 /var/lib/dpkg/status

Notice the amd64 arch.  So what the question really is about?

If you have found a place where Git explicitly uses a 32-bit integer where it would better be using a 64-bit one, please propose a patch to discuss.