Re: "There are too many unreachable loose objects" - why don't we run 'git prune' automatically?

2017-06-20 Thread Jeff King
On Sun, Jun 18, 2017 at 03:22:29PM +0200, Lars Schneider wrote: > > To be honest, the fact that we have to write this warning at all is a > > sign that Git is not doing a very good job. The best place to spend > > effort would be to teach git-gc to pack all of the unreachable objects > > into a

Re: "There are too many unreachable loose objects" - why don't we run 'git prune' automatically?

2017-06-18 Thread Lars Schneider
> On 10 Jun 2017, at 10:06, Jeff King wrote: > > On Fri, Jun 09, 2017 at 02:03:18PM +0200, Lars Schneider wrote: > >>> I agree the existing message isn't great. There should probably be a big >>> advise() block explaining what's going on (and that expert users can >>> disable).

Re: "There are too many unreachable loose objects" - why don't we run 'git prune' automatically?

2017-06-10 Thread Jeff King
On Fri, Jun 09, 2017 at 02:03:18PM +0200, Lars Schneider wrote: > > I agree the existing message isn't great. There should probably be a big > > advise() block explaining what's going on (and that expert users can > > disable). > > How about this? > > diff --git a/builtin/gc.c b/builtin/gc.c >

Re: "There are too many unreachable loose objects" - why don't we run 'git prune' automatically?

2017-06-09 Thread Lars Schneider
> On 09 Jun 2017, at 07:27, Jeff King wrote: > > On Thu, Jun 08, 2017 at 02:45:48PM +0200, Lars Schneider wrote: > >> I recently ran into "There are too many unreachable loose objects; run >> 'git prune' to remove them." after a "Auto packing the repository in >> background

Re: "There are too many unreachable loose objects" - why don't we run 'git prune' automatically?

2017-06-08 Thread Jeff King
On Thu, Jun 08, 2017 at 02:45:48PM +0200, Lars Schneider wrote: > I recently ran into "There are too many unreachable loose objects; run > 'git prune' to remove them." after a "Auto packing the repository in > background for optimum performance." message. > > This was introduced with a087cc9

"There are too many unreachable loose objects" - why don't we run 'git prune' automatically?

2017-06-08 Thread Lars Schneider
Hi, I recently ran into "There are too many unreachable loose objects; run 'git prune' to remove them." after a "Auto packing the repository in background for optimum performance." message. This was introduced with a087cc9 "git-gc --auto: protect ourselves from accumulated cruft" but I don't