You don’t loose anything by redoing the compression. I’m surprised the importer 
didn’t do that as the final pass. The issue is that as commits are added 
incrementally git sometimes can’t spot good compression choices. Running it 
after creation allows for more deltas to be examined.

You will need to repush the repo but none of the history will change so this 
isn’t a huge problem.

> On Sep 24, 2017, at 07:24, Bill Deegan <b...@baddogconsulting.com> wrote:
> 
> Also would I need to discard the current repo and create another to push this 
> back to?
> 
> On Sun, Sep 24, 2017 at 10:22 AM, Bill Deegan <b...@baddogconsulting.com 
> <mailto:b...@baddogconsulting.com>> wrote:
> I've not compressed a git repo before, do we lose any information?
> 
> -Bill
> 
> On Sun, Sep 24, 2017 at 7:54 AM, anatoly techtonik <techto...@gmail.com 
> <mailto:techto...@gmail.com>> wrote:
> I pushed my repository to https://github.com/techtonik/sconsize 
> <https://github.com/techtonik/sconsize>
> and now git clone downloads only 9 Mb instead of 100 Mb,
> 
>     $ git clone https://github.com/techtonik/sconsize 
> <https://github.com/techtonik/sconsize>
>     ...
>     Receiving objects: 100% (50034/50034 <tel:%2850034%2F50034>), 9.08 MiB | 
> 1.48 MiB/s, done.
> 
> Cloning official repo still takes 10 times longer.
> 
>     $ git clone https://github.com/SConsProject/scons 
> <https://github.com/SConsProject/scons>
>     ...
>     Receiving objects: 100% (51561/51561 <tel:%2851561%2F51561>), 109.12 MiB 
> | 1.06 MiB/s, done.
> 
> 
> 
> On Sun, Sep 24, 2017 at 2:12 PM, Dirk Bächle <tshor...@gmx.de 
> <mailto:tshor...@gmx.de>> wrote:
> > Anatoly,
> >
> >
> > this isn't quite correct. The figures you show here are for
> >
> >     - removing the docbook folder, AND
> >
> >     - compressing the repository.
> >
> > Your pastebin shows that you don't run a compression *before* removing
> > docbook. If I do a fresh checkout:
> >
> >     git clone https://github.com/SConsProject/scons 
> > <https://github.com/SConsProject/scons>
> >
> > and then a
> >
> >     git reflog expire --expire=now --all && git gc --prune=now --aggressive
> >
> > I get
> >
> >     git count-objects -vH
> >
> >     ...
> >
> >     size-pack: 12.26 MiB
> >
> > So, compressing the repo is a good idea in general, and I'm totally for it.
> > But removing docbook (which isn't easily possible anyway because our doc
> > toolchain relies on it currently) would save us only 2MB roughly.
> >
> > Regards,
> >
> >
> > Dirk
> >
> >
> > On 24.09.2017 10 <tel:24.09.2017%2010>:50, anatoly techtonik wrote:
> >>
> >> Just removing docbook-xsl-1.76.1 brings compressed repository
> >> size from 110.50 MiB down to 10.45 MiB
> >>
> >> https://pastebin.mozilla.org/9068127 <https://pastebin.mozilla.org/9068127>
> >>
> >> On Sun, Sep 24, 2017 at 10:50 AM, anatoly techtonik <techto...@gmail.com 
> >> <mailto:techto...@gmail.com>>
> >> wrote:
> >>>
> >>> HI Bill.
> >>>
> >>> History is ok, but repository size is now too big.
> >>>
> >>>      Receiving objects: 100% (51561/51561 <tel:%2851561%2F51561>), 109.12 
> >>> MiB | 1.08 MiB/s,
> >>> done.
> >>>
> >>> We should take the opportunity to clean up binaries
> >>> and huge commits made by mistake. I am trying to
> >>> see what are they.
> >>>
> >
> > _______________________________________________
> > Scons-dev mailing list
> > Scons-dev@scons.org <mailto:Scons-dev@scons.org>
> > https://pairlist2.pair.net/mailman/listinfo/scons-dev 
> > <https://pairlist2.pair.net/mailman/listinfo/scons-dev>
> 
> 
> 
> --
> anatoly t.
> _______________________________________________
> Scons-dev mailing list
> Scons-dev@scons.org <mailto:Scons-dev@scons.org>
> https://pairlist2.pair.net/mailman/listinfo/scons-dev 
> <https://pairlist2.pair.net/mailman/listinfo/scons-dev>
> 
> 
> _______________________________________________
> Scons-dev mailing list
> Scons-dev@scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev

_______________________________________________
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Reply via email to