{"thread":{"id":"4669","subject":"Re: [RFC] git-fetch - repack in the background after fetching","startedAt":"2006-06-25T17:53:16Z","lastAt":"2006-06-25T17:53:16Z","messageCount":1,"participants":["linux@horizon.com"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"22575","messageId":"20060625175316.26403.qmail@science.horizon.com","threadId":"4669","inReplyTo":null,"subject":"Re: [RFC] git-fetch - repack in the background after fetching","fromName":"","fromEmail":"linux@horizon.com","sentAt":"2006-06-25T17:53:16Z","receivedAt":"2006-06-25T17:53:16Z","isPatch":false,"sender":{"key":"linux@horizon.com","avatar":null},"body":"How about a post-fetch hook script that can do this?  With an example\nof either printing a message or repacking in the background?\n\nprocmail includes a lockfile(1) utility useful for shell scripts, but\nit also wouldn't be hard to add a \"git-lock-file <file> <command>...\"\nutility that would create the given lock file, fork the command, and\nclean up again when it exited, relaying its exit status.\n(I can write one if there's interest.)\n\nI agree with Linus that *defaulting* to background repack has problems,\nbut it does seem useful to provide enough hooks to easily implement\nthe option.  Even printing the warning in a script seems like it would\nsimplify internationalization, and different sites (e.g. reiserfs\ndevelopers) might have different policies about what constitutes\n\"a boatload\".\n"}]}