From: Jean-Michel MERCIER <jeanmichel.mercier@newsbridge.io>
To: "brian m. carlson" <sandals@crustytoothpaste.net>,
Jean-Michel MERCIER <jeanmichel.mercier@newsbridge.io>,
git@vger.kernel.org
Subject: Re: feature-request: silently stops ssh-agent.exe when upgrading (windows)
Date: Fri, 16 Dec 2022 08:53:19 +0100 [thread overview]
Message-ID: <CAOLx1Biwd9KzqipoEPaw0M2AecW7XfuyvNeVW4F59e696gMt-Q@mail.gmail.com> (raw)
In-Reply-To: <Y5u/E04V0QWQTDhu@tapette.crustytoothpaste.net>
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@crustytoothpaste.net> 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
next prev parent reply other threads:[~2022-12-16 7:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 8:38 feature-request: silently stops ssh-agent.exe when upgrading (windows) Jean-Michel MERCIER
2022-12-16 0:42 ` brian m. carlson
2022-12-16 7:53 ` Jean-Michel MERCIER [this message]
[not found] ` <CAOLx1Bi189tdo1Yn7njv9BjMzjuVOT8MSZH-bx8o-nS6gQpQTg@mail.gmail.com>
2022-12-21 15:58 ` Jean-Michel MERCIER
2022-12-22 2:45 ` Bagas Sanjaya
2022-12-22 5:19 ` Eric Sunshine
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOLx1Biwd9KzqipoEPaw0M2AecW7XfuyvNeVW4F59e696gMt-Q@mail.gmail.com \
--to=jeanmichel.mercier@newsbridge.io \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).