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

Re: [RFC] git-fetch - repack in the background after fetching

From
Llinux@horizon.com <linux@horizon.com>
Date
Jun 25, 2006, 17:53 UTC
Message-ID
<20060625175316.26403.qmail@science.horizon.com>

How about a post-fetch hook script that can do this? With an example of either printing a message or repacking in the background?

procmail includes a lockfile(1) utility useful for shell scripts, but it also wouldn't be hard to add a "git-lock-file <file> <command>..." utility that would create the given lock file, fork the command, and clean up again when it exited, relaying its exit status. (I can write one if there's interest.)

I agree with Linus that *defaulting* to background repack has problems, but it does seem useful to provide enough hooks to easily implement the option. Even printing the warning in a script seems like it would simplify internationalization, and different sites (e.g. reiserfs developers) might have different policies about what constitutes "a boatload".

Message 1 of 1 in “Re: [RFC] git-fetch - repack in the background after fetching”
  1. linux@horizon.comJun 25, 2006

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.