time to update with new packs

Tony Luck· Oct 1, 2005, 04:40 UTC · lore

I see that Linus made a new incremental pack when he released 2.6.14-rc3 ... so to be nice to the kernel.org mirroring daemons I should make use of them.

After the excitement I had last time with packs and trying to make use of alternate directories, I thought I'd check the process before I touched anything.

1) Link the new pack files from Linus' objects/pack directory
to my objects/pack directory.

2) $ GIT_DIR=. git prune-packed # in my directory

3) $ GIT_DIR=. git update-server-info # ditto

Ok?

-Tony

Junio C Hamano· Oct 1, 2005, 07:18 UTC · re: Tony Luck · lore

Re: time to update with new packs

Tony Luck <tony.luck@gmail.com> writes:

Show 6 quoted lines

> 1) Link the new pack files from Linus' objects/pack directory
> to my objects/pack directory.
>
> 2) $ GIT_DIR=. git prune-packed # in my directory
>
> 3) $ GIT_DIR=. git update-server-info # ditto

When everybody uses more recent clients, you could say "/pub/scm/.../torvalds/linux-2.6.git/objects" in your objects/info/alternates file and not worry about step (1). git native transport has known about the alternate mechanism since the inception. The alternate mechanism support in "git fetch" and "git clone" for rsync and http transports is a relatively recent addition (appeared just before 0.99.7).

So (1) is not necessary for git native transport once you have "alternate" file, but for other transports (1) is probably still helpful at this point.

Also, enabling hooks/post-update in your public repository would save you from worrying about (3), provided if the only way you update it is by pushing into it, which I think is what usually people are doing.