|Re: [hatari-devel] Hatari download page changed unexpectedly|
[ Thread Index |
| More lists.tuxfamily.org/hatari-devel Archives
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] Hatari download page changed unexpectedly
- From: Thomas Huth <th.huth@xxxxxxxxx>
- Date: Thu, 14 Feb 2019 11:52:27 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1550141553; bh=NJDXCbZjUpXSqXsmGX7UFEFZZDMXUec4uuP5rJt/dGY=; h=Subject:To:From:Date:From; b=WJpaUOs6jkprbjeCYlVlviknZ1sfYKWisZB5gWtr3q5pkaLMAwzToapmgLXV1mjaG J7f6cM5DG2Mh6r5r3SoJY4Tzye7dMxTiRJGZR4tREFcqJGRaTBwNiVHqZlEenBT+Bv MYDDQX94d5fBPEs/p/3cq3o1CAHaX/WIMiND26W4ZHdv9CBHXlW78LPhZHr9md6i9b IJOm/xzsjw4FMV2LzaGrUECW8oaM9XnF6vBgQz81YR+fw6IIVudC0ZndqeDQtD7wRN 4ah+9QN9imYrBDmFb1sdnrpABK7kmEeywPAU/15lVaSf+YE2WV0q+y51kTOG+2cNOc sIPkFf/aOqHxQ==
On 14/02/2019 09.31, Christer Solskogen wrote:
> On Thu, Feb 14, 2019 at 6:02 AM Thomas Huth <th.huth@xxxxxxxxx
> <mailto:th.huth@xxxxxxxxx>> wrote:
> Am Tue, 12 Feb 2019 15:38:29 +0100
> schrieb Nicolas Pomarède <npomarede@xxxxxxxxxxxx
> > Le 12/02/2019 à 15:32, Christer Solskogen a écrit :
> > > running "git gc" will in fact optimize space, but repo only
> > > goes from ~108 MB to 93 MB. Don't know if there's a better way to
> > > compress ?
> > >
> > >
> > > git gc --aggressive
> > Indeed, size went from 93 MB to 12 MB this time :)
> > I guess size will expand after some commits and the command can be
> > run again, but it's better to have a small repo when you want to do a
> > quick local "clone" of the repo by just doing "cp -r repo repo_new"
> That size is really a little bit weird. I guess it must have grown that
> big on my HD since I used to sync my git tree with "hg-fast-export"
> with the mercurial tree since last summer. Sorry for that.
> I'm a little bit afraid that the repo on the server is now also 120 MB
> big already. I wonder whether we can somehow trigger the garbage
> collection on the server side, too? Or should we maybe rather destroy
> the repo again and start with a fresh and small one?
That seems to be specific to bitbucket, and also does not work on
tuxfamily -- forced pushes are not allowed here (and I did not see an
option to enable them).
Anyway, I've raised a question in the support forum now:
Let's see whether they've got a solution. If not, I think we should
delete and re-init the repo again.