{"thread":{"id":"50092","subject":"Suppress reporting implicit git gc calls, when they don’t do anything","startedAt":"2018-12-21T10:36:43Z","lastAt":"2018-12-21T10:36:43Z","messageCount":1,"participants":["Дилян Палаузов"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"365723","messageId":"63142a981325e68cb6e90ebd485627e41321ecaa.camel@aegee.org","threadId":"50092","inReplyTo":null,"subject":"Suppress reporting implicit git gc calls, when they don’t do anything","fromName":"Дилян Палаузов","fromEmail":"dilyan.palauzov@aegee.org","sentAt":"2018-12-21T10:27:19Z","receivedAt":"2018-12-21T10:36:43Z","isPatch":false,"sender":{"key":"dilyan.palauzov@aegee.org","avatar":null},"body":"Hello,\n\nWith git 19.2.2 after `git pull` the output was\n1. Autopacking the repository in background for optimal performance. \nSee \"git help gc\" for manual housekeeping\n\n2. error: Your local changes to the following files would be\noverwritten by merge:\n  …\nPlease commit your changes or stash them before you merge.\nAborting\n\nThis implies, that `git gc` runs in the background.\n\nThen I called `git rebase --autostash` on which the output contained\nagain:\n\n“Autopacking the repository in background for optimal performance.  See\n\"git help gc\" for manual housekeeping.”\n\nThe second message means, that `git gc` is again started in the\nbackground, before the first GC has finished.  Clearly non-sense.\n\nIn practice, the second GC does not run, or exits very fast.\n\n* Alter `git rebase --autostash` not to write, that git gc is called,\nwhen that GC doesn’t do anything.\n\nRegards\n  Дилян\n\n"}]}