Re: [PATCH v5 2/4] Change GIT_ALLOC_LIMIT check to use git_parse_ulong()
- From
Jeff King <peff@peff.net>
- Date
- Aug 25, 2014, 15:12 UTC
- Message-ID
- <20140825151200.GC28176@peff.net>
- In-Reply-To
- <7D29D002-6357-4060-90DF-3993D259C475@zib.de>
On Mon, Aug 25, 2014 at 05:06:22PM +0200, Steffen Prohaska wrote:
> I think it's reasonable that GIT_ALLOC_LIMIT=0 means "no limit", so that > the limit can easily be disabled temporarily.
IMHO, GIT_ALLOC_LIMIT= (i.e., the empty string) would be a good way to say that (and I guess that even works currently, due to the way atoi works, but I suspect git_parse_ulong might complain). It is probably not worth worrying about too much. This is not even a user-facing interface, and the test scripts just set it to 0.
So I'd be OK going that direction, or just leaving it as-is.
-Peff