I was playing with a hook for file size limits that wanted to store the
limit in git-config. It turns out we don't do a very good job of big
integers:
$ git config foo.size 2g
$ git config --int foo.size
-2147483648
Oops. After this series, we properly notice the error:
$ git config
On 08/21/2013 12:39 AM, Jeff King wrote:
I was playing with a hook for file size limits that wanted to store the
limit in git-config. It turns out we don't do a very good job of big
integers:
$ git config foo.size 2g
$ git config --int foo.size
-2147483648
Oops. After this series,
On Wed, Aug 21, 2013 at 12:44:22AM +0200, Stefan Beller wrote:
On 08/21/2013 12:39 AM, Jeff King wrote:
I was playing with a hook for file size limits that wanted to store the
limit in git-config. It turns out we don't do a very good job of big
integers:
$ git config foo.size 2g
Jeff King p...@peff.net writes:
I was playing with a hook for file size limits that wanted to store the
limit in git-config. It turns out we don't do a very good job of big
integers:
$ git config foo.size 2g
$ git config --int foo.size
-2147483648
Oops. After this series, we
Junio C Hamano gits...@pobox.com writes:
Jeff King p...@peff.net writes:
I was playing with a hook for file size limits that wanted to store the
limit in git-config. It turns out we don't do a very good job of big
integers:
$ git config foo.size 2g
$ git config --int foo.size
On Tue, Aug 20, 2013 at 04:06:19PM -0700, Junio C Hamano wrote:
Jeff King p...@peff.net writes:
I was playing with a hook for file size limits that wanted to store the
limit in git-config. It turns out we don't do a very good job of big
integers:
$ git config foo.size 2g
$ git
On Tue, Aug 20, 2013 at 04:41:30PM -0700, Junio C Hamano wrote:
If this applied on the writing side, I would understand it very
much, i.e.
$ git config --int32 foo.size 2g
fatal: 2g is too large to be read as int32.
It does, by the way. When you request a type on the writing
7 matches
Mail list logo
