From: Patrik Gornicz <patrik-git@mail.pgornicz.com>
To: Sebastian Schuberth <sschuberth@gmail.com>
Cc: Joshua Jensen <jjensen@workspacewhiz.com>,
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 16:49:27 -0400 [thread overview]
Message-ID: <5144DAD7.50203@mail.pgornicz.com> (raw)
In-Reply-To: <51447052.1020407@gmail.com>
On 03/16/13 09:14, Sebastian Schuberth wrote:
> 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.
I attempted to do just this about a month ago though things really
started to snowball. To get openssh to compile you need to update a
bunch of other programs in the msys branch and I just lost interest in
doing so. More info can be found in the msysgit issue "Upgrade SSH" [1].
> 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].
Any idea as to when this mingwGitDevEnv project will be mature enough to
use as a replacement for msysgit? One of the reasons I gave up trying to
tweak things to get openssh compiling was that this seemed like a much
better idea. Though if it's fair off I might find time to give it
another shot.
> [1] https://github.com/sschuberth/mingwGitDevEnv
> [2] https://github.com/sschuberth/mingwGitDevEnv/pull/5
If someone is keen to try and update openssh in msysgit I'd be willing
to share my hacks from a month ago which could be used as a starting
point. It was left nowhere near ready for a pull request, partially due
to binary issues mentioned above, but at least it'll provide reasonable
ideas to a few of the things that need to happen.
[1] https://github.com/msysgit/msysgit/issues/31
Patrik
next prev parent reply other threads:[~2013-03-16 20:55 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
2013-03-16 20:49 ` Patrik Gornicz [this message]
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=5144DAD7.50203@mail.pgornicz.com \
--to=patrik-git@mail.pgornicz.com \
--cc=git@vger.kernel.org \
--cc=jjensen@workspacewhiz.com \
--cc=kostix+git@007spb.ru \
--cc=kristof@kristofmattei.be \
--cc=sschuberth@gmail.com \
/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).