Re: [RFC] git-fetch - repack in the background after fetching
- From
Junio C Hamano <junkio@cox.net>
- Date
- Jun 25, 2006, 03:12 UTC
- Message-ID
- <7vy7vmormn.fsf@assigned-by-dhcp.cox.net>
- In-Reply-To
- <11511486003924-git-send-email-martin@catalyst.net.nz>
Martin Langhoff <martin@catalyst.net.nz> writes:
> This is a follow up to a similar patch earlier > http://www.gelato.unsw.edu.au/archives/git/0605/21401.html -- is there > interest in making GIT more friendly to users who don't know or care > about packing and repacking their repos?
I would be a bit worried about the niced background repack racing against another instance of itself spawned by the same parent.
> I loathe to do this conditionally only on the count of unpacked > objects. If there's a quick'n'dirty way of asking portably whether > the machine is busy or otherwise resource-constrained (ie: on battery) > it should use it to avoid running repack at inconvenient times.
count-objects might be lighter weight than rev-list --unpacked.
If you mean to make core.autorepack to be boolean, checking for string 'no' is not the right way.
git repo-config --bool --get core.autorepack
But it does not matter if that variable is a string that is almost always true unless the value is "no".