On 27/03/2023 10:17, Johannes Schindelin wrote: > Hi Pau & Junio, > > this patch series saw a positive review from Junio (thank you! I know that > you try to stay away from Tcl code, so I appreciate the effort very much), > but apart from that it simply languished on the mailing list for more than > two months now. > > Paul, is there anything I can do to help you integrate this into `gitk`? > Or is it time to pass over `gitk` maintenance to the Git project? > > Ciao, > Johannes I just tripped over this problem while trying to de-stack my Git backlog https://github.com/git-for-windows/git/issues/4408 "sdk gitk interaction". > > On Tue, 24 Jan 2023, Johannes Schindelin via GitGitGadget wrote: > >> These patches have been cooking for such a long time in Git for Windows that >> you might think they turned into broth. Yummy broth, to be sure. But broth. >> 'Tis beyond time for the patches to make it upstream. >> >> Johannes Schindelin (1): >> gitk: prevent overly long command lines >> >> Nico Rieck (1): >> gitk: escape file paths before piping to git log >> >> gitk | 36 +++++++++++++++++++++++++++++++----- >> 1 file changed, 31 insertions(+), 5 deletions(-) >> >> >> base-commit: 465f03869ae11acd04abfa1b83c67879c867410c >> Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-1469%2Fdscho%2Fgitk-long-cmdline-v1 >> Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1469/dscho/gitk-long-cmdline-v1 >> Pull-Request: https://github.com/gitgitgadget/git/pull/1469 >> -- >> gitgitgadget >> If there was a way to un-stick this [1] it would be great. Philip [1] https://lore.kernel.org/git/pull.1469.git.1674559397.gitgitgadget@xxxxxxxxx/
