{"thread":{"id":"58817","subject":"[Q] Where does \"git commit -q -m msg\" spend time?","startedAt":"2022-11-19T00:24:06Z","lastAt":"2022-11-19T00:24:06Z","messageCount":1,"participants":["Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"467545","messageId":"xmqqbkp3kf5y.fsf@gitster.g","threadId":"58817","inReplyTo":null,"subject":"[Q] Where does \"git commit -q -m msg\" spend time?","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2022-11-18T23:37:29Z","receivedAt":"2022-11-19T00:24:06Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"On a slow filesystem it gets more noticeable, but I have been\nwondering (without a debugger or a profiler, as I am supposed to be\non vacation) for the past few weeks why these two commands in the\nsame repository perform very differently:\n\n    $ git write-tree\n    $ git commit -q -m msg\n\nEspecially even after running the former, running the latter, which\nI naïvely thought that it only needs to create a commit object with\n\"msg\" and wrapping the result of the former (which is more-or-less\ninstant) into it, and do nothing else.\n"}]}