There's advantage to repacking a repository after using git-fast-import. If that repacked repository is then git-pushed to another, is there any point in repacking the other afterwards? I'm guessing not, but just checking.
P.
Karl HasselströmRe: When to repack?
On 2008-02-29 10:55:41 +0000, Paul Gardiner wrote:
> There's advantage to repacking a repository after using > git-fast-import. If that repacked repository is then git-pushed to > another, is there any point in repacking the other afterwards? I'm > guessing not, but just checking.
No, there isn't. The pack is essentially sent unmodified over the wire. (IIRC, packs were originally conceived as a way of reducing transfer bandwidth, and were later adopted for on-disk storage as well. But I might be mistaken.)
--
Karl Hasselström, kha@treskal.com
www.treskal.com/kalle
Jakub NarebskiRe: When to repack?
Paul Gardiner <osronline@glidos.net> writes:
> There's advantage to repacking a repository after using git-fast-import. > If that repacked repository is then git-pushed to another, is there > any point in repacking the other afterwards? I'm guessing not, but > just checking.
Yes, there is, to concatenate packs. But this should be less urgent.
-- Jakub Narebski Poland ShadeHawk on #git
Re: When to repack?
There's advantage to repacking a repository after using git-fast-import. If that repacked repository is then git-pushed to another, is there any point in repacking the other afterwards? I'm guessing not, but just checking.
I am not an expert but I would not do it afterwards too.
Xavier
-- http://www.gnu.org http://www.april.org http://www.lolica.org