git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Do not run git-pack-refs by default for now from git-gc

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Feb 13, 2007, 10:03 UTC
Message-ID
<Pine.LNX.4.63.0702131101400.1300@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<7vzm7iz8uv.fsf@assigned-by-dhcp.cox.net>
Hi,
On Tue, 13 Feb 2007, Junio C Hamano wrote:
> Just to be on the safe side, let's not run pack-refs from git-gc
> without an explicit "[gc] packrefs = true" configuration.

It seems to me that the reason are dumb transports, which are very likely to run only from bare repositories. How about checking for a bare repository explicitely, and only if it _is_ bare, check for gc.packrefs, too?

Packed refs _do_ have a tremendous advantage (when you have a lot of tags, like many CVS switchers).

Ciao, Dscho

Previous: Junio C HamanoNext: Jeff King
Message 3 of 9 in “linux-2.6.git/packed-refs???”
  1. Junio C HamanoFeb 13, 2007
  2. Do not run git-pack-refs by default for now from git-gcJunio C Hamano, Feb 13, 2007
  3. Johannes SchindelinFeb 13, 2007
  4. Jeff KingFeb 13, 2007
  5. Johannes SchindelinFeb 13, 2007
  6. Junio C HamanoFeb 13, 2007
  7. git-gc: run pack-refs by default unless the repo is bareJohannes Schindelin, Feb 13, 2007
  8. Theodore TsoFeb 13, 2007
  9. Johannes SchindelinFeb 13, 2007

Read the whole thread, see it on lore, or plain text.

$ 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.