From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Sam Vilain" <sam@vilain.net>
Cc: "Nicolas Pitre" <nico@cam.org>, "Dana How" <danahow@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: [PATCH] [RFC] Generational repacking
Date: Fri, 8 Jun 2007 10:51:53 +1200 [thread overview]
Message-ID: <46a038f90706071551w45592471g59a35abb871749bd@mail.gmail.com> (raw)
In-Reply-To: <46687A73.6080100@vilain.net>
On 6/8/07, Sam Vilain <sam@vilain.net> wrote:
> Ok. But if repack is generational you probably don't mind waiting for
> it on commit so don't need to background it.
Agreed. The patch I posted back then was on fetch as a signle fetch is
more likely to bring a lot of new objects in. (Moreso than a commit)
Repack-on-commit if there's more than 1k unpacked objects makes sense.
Are fetches nowaways always using the "keep pack" and "fatten thin
pack" semantics? If yes, then
cheers,
martin
next prev parent reply other threads:[~2007-06-07 22:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 11:08 [PATCH] [RFC] Generational repacking Sam Vilain
2007-06-06 22:46 ` Junio C Hamano
2007-06-06 22:53 ` Sam Vilain
2007-06-07 0:04 ` Dana How
2007-06-07 2:28 ` Sam Vilain
2007-06-07 3:20 ` Nicolas Pitre
2007-06-07 5:13 ` Sam Vilain
2007-06-07 13:38 ` Nicolas Pitre
2007-06-07 21:29 ` Sam Vilain
2007-06-07 19:46 ` Martin Langhoff
2007-06-07 21:36 ` Sam Vilain
2007-06-07 22:51 ` Martin Langhoff [this message]
2007-06-07 3:05 ` Nicolas Pitre
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=46a038f90706071551w45592471g59a35abb871749bd@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=danahow@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nico@cam.org \
--cc=sam@vilain.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).