From: Eric Wong <normalperson@yhbt.net>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: "Karl Hasselström" <kha@treskal.com>,
git@vger.kernel.org, "Kevin Ballard" <kevin@sb.org>,
"Junio C Hamano" <gitster@pobox.com>
Subject: Re: [PATCH] Let "git svn" run "git gc --auto" occasionally
Date: Sat, 19 Jan 2008 19:37:37 -0800 [thread overview]
Message-ID: <20080120033737.GA7767@soma> (raw)
In-Reply-To: <1200783050.5724.196.camel@brick>
Harvey Harrison <harvey.harrison@gmail.com> wrote:
> On Sat, 2008-01-19 at 23:36 +0100, Karl Hasselström wrote:
> > Let "git svn" run "git gc --auto" every 100 imported commits, to
> > reduce the number of loose objects.
>
> I found 100 was a bit too low when doing some large repos, I've
> been using 1000. I'd argue that --repack=1000 should be done by
> default.
I've found 100 for repack too low in the past, too, which is why
repack defaults to 1000 if no number is specified. I think it
should hold for gc --auto, too.
> > I'm not quite sure how this should interact with the --repack flag.
> > Right now they just coexist, except for never running right after one
> > another, but conceivably we should do something cleverer. Eric?
I consider --repack is out-of-date now that we have gc --auto. I'm in
favor of ripping out repack support in git-svn and just using gc --auto.
> How about git gc always gets run at the very end of a git svn fetch?
I'd much prefer that we run gc --auto at the end of every fetch instead
of doing so randomly for small fetches.
--
Eric Wong
next prev parent reply other threads:[~2008-01-20 3:38 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 12:17 git-svn should default to --repack Kevin Ballard
2008-01-18 15:56 ` Karl Hasselström
2008-01-18 20:44 ` Junio C Hamano
2008-01-19 12:35 ` Karl Hasselström
2008-01-19 15:05 ` Kevin Ballard
2008-01-19 22:36 ` [PATCH] Let "git svn" run "git gc --auto" occasionally Karl Hasselström
2008-01-19 22:50 ` Harvey Harrison
2008-01-20 3:37 ` Eric Wong [this message]
2008-01-20 9:34 ` Karl Hasselström
2008-01-20 19:17 ` Junio C Hamano
2008-01-21 22:48 ` Eric Wong
2008-01-22 0:30 ` Junio C Hamano
2008-01-22 0:39 ` Eric Wong
2008-01-22 1:52 ` Junio C Hamano
2008-01-23 2:43 ` git filter-branch should run git gc --auto Kevin Ballard
2008-01-23 2:46 ` Junio C Hamano
2008-01-23 2:52 ` Junio C Hamano
2008-01-23 3:03 ` Kevin Ballard
2008-01-23 2:54 ` Harvey Harrison
2008-01-23 2:58 ` Kevin Ballard
2008-01-23 5:07 ` Sam Vilain
2008-01-23 8:18 ` Kevin Ballard
2008-01-23 6:44 ` Mike Hommey
2008-01-23 13:00 ` Johannes Schindelin
2008-01-23 19:22 ` Junio C Hamano
2008-02-03 16:55 ` [PATCH 0/2] "git svn" and "git gc --auto" Karl Hasselström
2008-02-03 16:56 ` [PATCH 1/2] git-svn: Don't call git-repack anymore Karl Hasselström
2008-02-03 16:56 ` [PATCH 2/2] Let "git svn" run "git gc --auto" occasionally Karl Hasselström
2008-01-20 21:39 ` [PATCH 1/2] git-svn: Don't call git-repack anymore Karl Hasselström
2008-01-20 21:40 ` [PATCH 2/2] Let "git svn" run "git gc --auto" occasionally Karl Hasselström
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=20080120033737.GA7767@soma \
--to=normalperson@yhbt.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=harvey.harrison@gmail.com \
--cc=kevin@sb.org \
--cc=kha@treskal.com \
/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).