From: Junio C Hamano <junkio@cox.net>
To: Martin Langhoff <martin@catalyst.net.nz>
Cc: git@vger.kernel.org
Subject: Re: [RFC] git-fetch - repack in the background after fetching
Date: Sat, 24 Jun 2006 20:12:32 -0700 [thread overview]
Message-ID: <7vy7vmormn.fsf@assigned-by-dhcp.cox.net> (raw)
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".
next prev parent reply other threads:[~2006-06-25 3:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-24 11:30 [RFC] git-fetch - repack in the background after fetching Martin Langhoff
2006-06-25 3:12 ` Junio C Hamano [this message]
2006-06-25 10:10 ` [PATCH] Repack should try to prevent itself from running twice, concurrently Ryan Anderson
2006-06-25 10:17 ` Johannes Schindelin
2006-06-25 3:53 ` [RFC] git-fetch - repack in the background after fetching Linus Torvalds
2006-06-25 9:25 ` Johannes Schindelin
2006-06-25 17:29 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2006-06-25 17:53 linux
2006-05-30 4:42 Martin Langhoff
2006-05-30 4:51 ` Linus Torvalds
2006-05-30 5:14 ` Martin Langhoff
2006-05-30 6:37 ` Daniel Barkalow
2006-05-30 14:53 ` Linus Torvalds
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vy7vmormn.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=martin@catalyst.net.nz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.