Re: [PATCH] Consolidate {receive,fetch}.unpackLimit

From: Shawn O. Pearce <spearce@spearce.org>
Date: Jan 25, 2007, 05:14 UTC
Message-ID: <20070125051419.GB20345@spearce.org>
In-Reply-To: <7v1wljc3hb.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano <junkio@cox.net> wrote:

Show 5 quoted lines

> This allows transfer.unpackLimit to specify what these two
> configuration variables want to set.
> 
> We would probably want to deprecate the two separate variables,
> as I do not see much point in specifying them independently.

Indeed. I was going to fix this too, but reuse receive.unpackLimit. From my point of view both fetch and receive-pack are recieving objects into this repository; and in either case I want the same behavior with regards to loose object/pack management.

-- 
Shawn.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.