{"thread":{"id":"53412","subject":"[RFC] subtree: say last line of progress when all commits has been processed","startedAt":"2020-05-06T13:12:54Z","lastAt":"2020-05-11T11:21:11Z","messageCount":2,"participants":["Claus Schneider","Tom Clarkson"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"397183","messageId":"CA+GP4brP8rtTxtKCPaq0q8VisOa9=fRJWU86SE61zB7S6CaGzw@mail.gmail.com","threadId":"53412","inReplyTo":"CA+GP4bpUs8ZArrf6sZDHDPHEJYu5Z_jrq4c5Bz4Sm6M24LuRMw@mail.gmail.com","subject":"[RFC] subtree: say last line of progress when all commits has been processed","fromName":"Claus Schneider","fromEmail":"claus.schneider@eficode.com","sentAt":"2020-05-06T13:12:40Z","receivedAt":"2020-05-06T13:12:54Z","isPatch":false,"sender":{"key":"claus.schneider@eficode.com","avatar":"https://avatars.githubusercontent.com/u/3347017?v=4"},"body":"Hi..\n\nCurrently the progress-bar when running split echo's with a single\nline which is great, but when it is done it disappears again and the\noutcome is gone.\n\nSuggest to record the last line and then \"say\" it after all commits\nhave been processed. It is then more informative to run from the\ncommand line.\n\nPatches can be found here:\nhttps://github.com/git/git/commit/5f0924bb2953b9ee084dbf72312bac6e7e556d83\n\nBest regards\nClaus Schneider\n"},{"id":"397530","messageId":"C681EF54-1CB9-4223-A59E-D2A7C9FE50DA@icloud.com","threadId":"53412","inReplyTo":"CA+GP4brP8rtTxtKCPaq0q8VisOa9=fRJWU86SE61zB7S6CaGzw@mail.gmail.com","subject":"Re: [RFC] subtree: say last line of progress when all commits has been processed","fromName":"Tom Clarkson","fromEmail":"tqclarkson@icloud.com","sentAt":"2020-05-11T11:11:28Z","receivedAt":"2020-05-11T11:21:11Z","isPatch":false,"sender":{"key":"tqclarkson@icloud.com","avatar":"https://gravatar.com/avatar/02ea2942fcaf5dc1140ccda995e0dee545ff210ca8adee02d50f35de7205e301?d=mp&s=160"},"body":"\n> On 6 May 2020, at 11:12 pm, Claus Schneider <claus.schneider@eficode.com> wrote:\n\n> Suggest to record the last line and then \"say\" it after all commits\n> have been processed. It is then more informative to run from the\n> command line.\n\nSeems reasonable enough. Looks like it might need an extra check on how it behaves in quiet mode, but other than that go ahead and try submitting a patch via GitGitGadget.\n\n"}]}