From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH 0/8] Updated git-gc --auto series.
Date: Mon, 17 Sep 2007 01:27:05 -0700 [thread overview]
Message-ID: <1190017633436-git-send-email-gitster@pobox.com> (raw)
An updated series of "git-gc --auto", on top of 'next',
consisting of 8 patches, will follow this message.
Differences from the previous round are:
- Earlier if you have too many unreachable loose objects,
automated gc would have tried to "repack -d -l" which would
not improve the situation at all every time it was run. It
now at least warns upon such a situation;
- pack-objects learned --keep-unreachable option which helps
"repack -a -d" not to lose packed but unreachable objects
while repacking existing packs into a new pack;
- repack learned -A option which is similar to -a but gives
--keep-unreachable to underlying pack-objects;
- "git-gc --auto" runs "git-repack -A -d -l" when there are too
many packs in the repository;
- These changes are documented ;-)
next reply other threads:[~2007-09-17 9:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-17 8:27 Junio C Hamano [this message]
2007-09-17 8:27 ` [PATCH 1/8] Export matches_pack_name() and fix its return value Junio C Hamano
2007-09-17 8:27 ` [PATCH 2/8] pack-objects --keep-unreachable Junio C Hamano
2007-09-17 8:27 ` [PATCH 3/8] repack -A -d: use --keep-unreachable when repacking Junio C Hamano
2007-09-17 8:27 ` [PATCH 4/8] git-gc --auto: move threshold check to need_to_gc() function Junio C Hamano
2007-09-17 8:27 ` [PATCH 5/8] git-gc --auto: add documentation Junio C Hamano
2007-09-17 8:27 ` [PATCH 6/8] git-gc --auto: protect ourselves from accumulated cruft Junio C Hamano
2007-09-17 8:27 ` [PATCH 7/8] git-gc --auto: restructure the way "repack" command line is built Junio C Hamano
2007-09-17 8:27 ` [PATCH 8/8] git-gc --auto: run "repack -A -d -l" as necessary Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2007-09-17 8:43 [PATCH 0/8] Updated git-gc --auto series Junio C Hamano
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=1190017633436-git-send-email-gitster@pobox.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
/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.