You may want to play with gc.pruneexpire. From man git-config:
> When git gc is run, it will call prune --expire 2.weeks.ago.
> Override the grace period with this config variable. The value
> "now" may be used to disable this grace period and always prune
> unreachable objects immediately.
2015-11-19 18:41 GMT+01:00 Steinar Bang <s...@dod.no>:
> >>>>> Igor Deyashkin <
> > What are you expect from git gc in your case?
> I didn't *expect* anyhing, but what I *hoped* for was a way for git to
> compress the repository as much as it could on each push.
> Ie. compress it as much as what I get when I cd into the bare repo on
> the remote and do a
> git gc --agressive --prune=now
> (which saves quite a bit of space on my org file repos, everytime I've
> tried it)
> If I can't get this using git configuration, I can get what I want on
> the remote by creating a cronjob that packs it every night. But that
> seems like a hack.
> Also it won't pack the repos of my work directories.
> > Seems like your remote repository havent any garbage commits. Am i not
> > right?
> I wasn't so much after the garbage collection, as the repacking.
> - Steinar
> You received this message because you are subscribed to the Google Groups
> "Git for human beings" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to git-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.