Re: [PATCH] gc --auto: do not lock refs in the background

Nguyễn Thái Ngọc Duy pclo...@gmail.com writes: 9f673f9 (gc: config option for running --auto in background - 2014-02-08) puts gc --auto in background to reduce user's wait time. Part of the garbage collecting is pack-refs and pruning reflogs. These require locking some refs and may abort

[PATCH] gc --auto: do not lock refs in the background

9f673f9 (gc: config option for running --auto in background - 2014-02-08) puts gc --auto in background to reduce user's wait time. Part of the garbage collecting is pack-refs and pruning reflogs. These require locking some refs and may abort other processes trying to lock the same ref. If gc

Re: [PATCH] gc --auto: do not lock refs in the background

On Sun, May 25, 2014 at 7:38 AM, Nguyễn Thái Ngọc Duy pclo...@gmail.com wrote: Keep running pack-refs and reflog --prune in foreground to stop parallel ref updates. The remaining background operations (repack, prune and rerere) should impact running git processes. Eck.. s/should impact/should