Re: [RFC] gc: correct gc.autoPackLimit documentation

Eric Wong writes: >> That's neither here nor there for the off-by-one in gc or its >> documentation, of course, but just FYI. > > I'm now inclined to fix the problem in gc and leave the > documentation as-is (unless it cause other problems...) I think that is the best in the

Re: [RFC] gc: correct gc.autoPackLimit documentation

Jeff King wrote: > On Sat, Jun 25, 2016 at 01:14:50AM +, Eric Wong wrote: > > > I'm not sure if this is the best approach, or if changing > > too_many_packs can be done without causing problems for > > hosts of big repos. > > > > ---8<- > > Subject: [PATCH] gc:

Re: [RFC] gc: correct gc.autoPackLimit documentation

On Sat, Jun 25, 2016 at 01:14:50AM +, Eric Wong wrote: > I'm not sure if this is the best approach, or if changing > too_many_packs can be done without causing problems for > hosts of big repos. > > ---8<- > Subject: [PATCH] gc: correct gc.autoPackLimit documentation > > I want to

[RFC] gc: correct gc.autoPackLimit documentation

I'm not sure if this is the best approach, or if changing too_many_packs can be done without causing problems for hosts of big repos. ---8<- Subject: [PATCH] gc: correct gc.autoPackLimit documentation I want to ensure there is only one pack in my repo to take advantage of pack bitmaps.