From: Sebastian Schuberth <sschuberth@gmail.com>
To: Joshua Jensen <jjensen@workspacewhiz.com>
Cc: Konstantin Khomoutov <kostix+git@007spb.ru>,
Kristof Mattei <kristof@kristofmattei.be>,
git@vger.kernel.org
Subject: Re: SSH version on Git 1.8.1.2 for Windows is outdated.
Date: Sat, 16 Mar 2013 14:14:58 +0100 [thread overview]
Message-ID: <51447052.1020407@gmail.com> (raw)
In-Reply-To: <51438058.7080204@workspacewhiz.com>
On 15.03.2013 21:11, Joshua Jensen wrote:
>> Yes, you should grab the msysGit (the Git for Windows build
>> environment) [2], tweak it to include the new OpenSSH binary, ensure it
>> builds and works OK and then send a pull request (or post your patchset
>> to the msysgit mailing list [3].
>>
> Wow, we can do that now?
>
> When I brought up the vastly improved performance from a newer SSH
> executable, I was told the only way to get it in would be to build from
> source [1].
"tweak it to include the new OpenSSH binary" is supposed to include the
step to adjust the release.sh script to grab the updated sources and
build the binary.
However, another option is to take a look at the new mingwGitDevEnv
project [1], which relies on mingw-get to retrieve binary packages. I
hopefully find soon the time to include OpenSSH 6.1p1 incl. HPN-SSH
patches [2].
[1] https://github.com/sschuberth/mingwGitDevEnv
[2] https://github.com/sschuberth/mingwGitDevEnv/pull/5
--
Sebastian Schuberth
next prev parent reply other threads:[~2013-03-16 13:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 10:05 SSH version on Git 1.8.1.2 for Windows is outdated Kristof Mattei
2013-03-15 17:03 ` Konstantin Khomoutov
2013-03-15 20:11 ` Joshua Jensen
2013-03-16 13:14 ` Sebastian Schuberth [this message]
2013-03-16 20:49 ` Patrik Gornicz
2013-03-16 20:54 ` Sebastian Schuberth
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51447052.1020407@gmail.com \
--to=sschuberth@gmail.com \
--cc=git@vger.kernel.org \
--cc=jjensen@workspacewhiz.com \
--cc=kostix+git@007spb.ru \
--cc=kristof@kristofmattei.be \
/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.
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 NNTP newsgroup(s).