Hi guys!
It looks like the periodic auto-repack backgrounds itself when it shouldn't
do so. This causes the command it has triggered as a part of to fail:
==
[~/linux](master)$ git pull --rebase
remote: Counting objects:
Adam Borowski kilob...@angband.pl writes:
Hi guys!
It looks like the periodic auto-repack backgrounds itself when it shouldn't
do so. This causes the command it has triggered as a part of to fail:
Yikes. In the meantime, I think you can turn gc.autodetach off as a
workaround, e.g.
$
On Fri, May 23, 2014 at 02:40:41PM -0700, Junio C Hamano wrote:
Adam Borowski kilob...@angband.pl writes:
It looks like the periodic auto-repack backgrounds itself when it shouldn't
do so. This causes the command it has triggered as a part of to fail:
Duy, 9f673f94 (gc: config option for
Adam Borowski kilob...@angband.pl writes:
On Fri, May 23, 2014 at 02:40:41PM -0700, Junio C Hamano wrote:
Adam Borowski kilob...@angband.pl writes:
It looks like the periodic auto-repack backgrounds itself when it shouldn't
do so. This causes the command it has triggered as a part of to
On Sat, May 24, 2014 at 4:40 AM, Junio C Hamano gits...@pobox.com wrote:
Duy, 9f673f94 (gc: config option for running --auto in background,
2014-02-08) turns to be not such a hot idea. Sure, if we kick it
off background after doing something heavy, immediately before
giving control back to
5 matches
Mail list logo
