Hi everyone Just for the record in the archive if anyone is finding this thread: It has been handled : https://github.com/git-for-windows/git/issues/4172 https://github.com/git-for-windows/build-extra/pull/453 Thanks Jean-Michel > On Fri, Dec 16, 2022 at 8:53 AM Jean-Michel MERCIER <jeanmichel.mercier@xxxxxxxxxxxxx> wrote: >> >> Hi Brian >> >> Many thanks for pointing me in the right direction. >> Sorry for bothering >> >> Keep the great work and have a great end of year time >> >> Cheers >> >> Jean-Michel >> >> On Fri, Dec 16, 2022 at 1:43 AM brian m. carlson >> <sandals@xxxxxxxxxxxxxxxxxxxx> wrote: >> > >> > On 2022-12-15 at 08:38:01, Jean-Michel MERCIER wrote: >> > > Hello >> > >> > Hey, >> > >> > > I've looked in the public-inbox archive without finding any similar request. >> > > >> > > I believe it is a bit annoying that upgrading git-scm always generates >> > > an error when ssh-agent.exe is still running. User than have to open >> > > the Task Manager, find the task and kill it. >> > > >> > > Could you consider silently stopping ssh-agent during an upgrade, and >> > > may be restarting it afterward ? >> > > Most installer do that or at least offer the user to do it to allow >> > > seamless upgrading. >> > >> > The Git project doesn't distribute any binaries at all, and it doesn't >> > distribute OpenSSH. It distributes source code for Git, and that's >> > all. >> > >> > It sounds like you're using Git for Windows, which does distribute >> > binaries, both of Git and OpenSSH. If you have feedback for them, >> > you'll probably want to use their issue tracker >> > (https://github.com/git-for-windows/git/issues) and, if it hasn't >> > already been reported, you can request a change there. >> > -- >> > brian m. carlson (he/him or they/them) >> > Toronto, Ontario, CA
