This is the mail archive of the
mailing list for the GDB project.
Re: git is live
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Samuel Bronson <naesten at gmail dot com>
- Cc: gdb at sourceware dot org
- Date: Fri, 10 Jan 2014 08:53:33 +0200
- Subject: Re: git is live
- Authentication-results: sourceware.org; auth=none
- References: <877gd5iyaz dot fsf at fleche dot redhat dot com> <CAHACq4o_Lgy7G5c9rRLB1tijmEngrOn8UgsQVdrnk9j8o1=D1A at mail dot gmail dot com> <5266CCDC dot 6090803 at redhat dot com> <CAHACq4qqw4MZznnW7zAnOMW2kHEYRRyymAphoEiY1Of5Qeks8w at mail dot gmail dot com> <87iowgalle dot fsf at fleche dot redhat dot com> <CAHACq4pfgqZ9kso-+LTw2CmZGjoq-FKmt7NACEqj=X563obccQ at mail dot gmail dot com> <52700B95 dot 5060209 at redhat dot com> <87li1b7u4n dot fsf at fleche dot redhat dot com> <loom dot 20140110T034428-219 at post dot gmane dot org>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: Samuel Bronson <email@example.com>
> Date: Fri, 10 Jan 2014 02:55:36 +0000 (UTC)
> > git reflog expire --expire=now --all
> > git gc --prune=now --aggressive
> > --aggressive takes a lot of time though.
> I don't think --aggressive does what you think it does. They tell me that
> using "git repack" with some flags (or even no flags) is nearly always
> preferable; see:
That article is old (2007!) and outdated. Look into the source of
git-gc, and you will see that it actually invokes git-repack with the
exact options recommended by the article.
> (But of course you would certainly still want pruning to happen, but "git
> repack" can do that too; for example, try "git repack -a".)
Again, "git gc --aggressive" does that, too.