[IPython-dev] Making our git repo much smaller?

[MinRK]

I've looked into this a little bit, and as far as I can tell (though not
said with any confidence), the only option you have to repack a public repo
is to pull, repack, and then push to an entirely new repo and toss out the
old one - less than ideal.

-MinRK

On Tue, Feb 8, 2011 at 19:27, Robert Kern <robert.kern at gmail.com> wrote:

> On 2011-02-08 19:56 , Fernando Perez wrote:
>
> > I don't want to push blindly quite yet from my local copy, because I'm
> > not sure it's OK to do that.  I simply don't know enough: does it do
> > anything, does it do what we want, any damage?...
>
> That sums up most of my experience with git as a whole. ;-)
>
> My brief fiddling with my IPython checkout suggests that only the repack
> command
> does the major amount of compression (although following it up with gc is
> just
> good hygiene). None of those commands ought to do damage. Pushing to github
> doesn't seem to affect later checkouts, though. github does seem to run a
> standard no-options gc on every push, but they don't seem to repack.
>
>
> http://support.github.com/discussions/feature-requests/751-garbage-collection-or-repository-repack
>
> --
> Robert Kern
>
> "I have come to believe that the whole world is an enigma, a harmless
> enigma
>  that is made terrible by our own mad attempt to interpret it as though it
> had
>  an underlying truth."
>   -- Umberto Eco
>
> _______________________________________________
> IPython-dev mailing list
> IPython-dev at scipy.org
> http://mail.scipy.org/mailman/listinfo/ipython-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ipython-dev/attachments/20110208/17d4f4f8/attachment.html>