From: Shawn Pearce <spearce@spearce•org>
To: Junio C Hamano <junkio@cox•net>
Cc: git@vger•kernel.org
Subject: Re: [PATCH] Added --mirror-all to git-fetch.
Date: Wed, 20 Sep 2006 17:42:03 -0400 [thread overview]
Message-ID: <20060920214203.GE24415@spearce.org> (raw)
In-Reply-To: <7vslimfcf9.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox•net> wrote:
> Shawn Pearce <spearce@spearce•org> writes:
>
> >> > (the archive vs active repacking strategy we talked about,
> >>
> >> Hmm, I think I've missed this, I must look that in the archive.
> >
> > Junio pushed the core code out but nobody has done the Porecelain
> > for it. The basic idea is to prevent repacking every pack all of
> > the time; there's probably no reason to repack a 100 MiB pack file
> > every time you repack your loose objects so you might want to keep
> > say a <5 MiB "active pack" holding your recent created objects
> > and repack that frequently and a larger 100+ MiB "history pack"
> > holding everything else. Maybe you repack everything on a longer
> > time scale, such as once a year.
>
> And IIRC we were stuck on the convention to tell which ones are
> archives and which ones are actives (i.e. fair game for
> repacking). We were trying to figure out how to mark active
> ones (whose name changes every time you repack).
Yes. I had pretty much given up on a size threshold concept and
was thus in agreement with you that we just needed a way to flag
each pack file...
> I realized that there is a very simple and obvious solution for
> it. Introduce $GIT_OBJECT_DIRECTORY/info/archived-packs, a flat
> text file that lists the names of the archive packs. Any pack
> not listed there are active one and are subject to repacking.
Like that. :-)
--
Shawn.
prev parent reply other threads:[~2006-09-20 21:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-19 23:28 [PATCH] Added --mirror-all to git-fetch Shawn Pearce
2006-09-19 23:41 ` Petr Baudis
2006-09-20 16:06 ` Junio C Hamano
2006-09-20 16:14 ` Petr Baudis
2006-09-20 16:21 ` Shawn Pearce
2006-09-20 16:34 ` Junio C Hamano
2006-09-20 16:49 ` Shawn Pearce
2006-09-20 17:13 ` Junio C Hamano
2006-09-20 17:31 ` Shawn Pearce
2006-09-20 17:50 ` Junio C Hamano
2006-09-20 18:42 ` A Large Angry SCM
2006-09-20 18:29 ` Petr Baudis
2006-09-20 21:36 ` Junio C Hamano
2006-09-20 21:42 ` Shawn Pearce [this message]
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=20060920214203.GE24415@spearce.org \
--to=spearce@spearce$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
--cc=junkio@cox$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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