Hi Felipe,
On Tue, 22 Apr 2014, Felipe Contreras wrote:
> Johannes Schindelin wrote:
> > On Mon, 21 Apr 2014, Felipe Contreras wrote:
> > > Johannes Schindelin wrote:
> > > > Now, clearly you have all the motivation that is needed to get 64-bit
> > > > builds of Git for Windows going, and all the
Johannes Schindelin wrote:
> On Mon, 21 Apr 2014, Felipe Contreras wrote:
> > Johannes Schindelin wrote:
> > > Now, clearly you have all the motivation that is needed to get 64-bit
> > > builds of Git for Windows going, and all the motivation required to make
> > > sure that the MSVC support of the
Johannes Schindelin writes:
> On Mon, 21 Apr 2014, Felipe Contreras wrote:
>
>> Johannes Schindelin wrote:
>> > Now, clearly you have all the motivation that is needed to get 64-bit
>> > builds of Git for Windows going, and all the motivation required to make
>> > sure that the MSVC support of th
Hi,
On Mon, 21 Apr 2014, Felipe Contreras wrote:
> Johannes Schindelin wrote:
> > Now, clearly you have all the motivation that is needed to get 64-bit
> > builds of Git for Windows going, and all the motivation required to make
> > sure that the MSVC support of the msysGit project works.
>
> s/
Johannes Schindelin wrote:
> Now, clearly you have all the motivation that is needed to get 64-bit
> builds of Git for Windows going, and all the motivation required to make
> sure that the MSVC support of the msysGit project works.
s/msysGit/Git/
Personally I don't see why ideally I shouldn't be
Hi Sebastian,
On Mon, 21 Apr 2014, Sebastian Schuberth wrote:
> On 21.04.2014 00:10, Johannes Schindelin wrote:
>
> > tests do not pass yet. (I also would like to look into getting the
> > performance improvement Hannes Sixt achieved by his patch [*1*] into
> > mingwGitDevEnv's Git installation,
On 21.04.2014 00:10, Johannes Schindelin wrote:
tests do not pass yet. (I also would like to look into getting the
performance improvement Hannes Sixt achieved by his patch [*1*] into
mingwGitDevEnv's Git installation, too.)
Whoops. Footnote *1*: https://github.com/msysgit/msysgit/commit/a0f5d4
On Mon, 21 Apr 2014, Johannes Schindelin wrote:
> (I also would like to look into getting the performance improvement
> Hannes Sixt achieved by his patch [*1*] into mingwGitDevEnv's Git
> installation, too.)
Whoops. Footnote *1*: https://github.com/msysgit/msysgit/commit/a0f5d4f
--
To unsubscribe
Hi Heiko,
On Sat, 19 Apr 2014, Heiko Voigt wrote:
> Regarding mingwGitDevEnv[2]: That is a project started by Sebastian who
> also contributes to msysgit (and Git for Windows).
In fact, Sebastian is not only a contributor. He is co-maintainer of Git
for Windows.
> It eventually can (and probabl
On Sat, Apr 19, 2014 at 8:42 PM, Heiko Voigt wrote:
> But AFAIK its not ready for production use yet. I guess Sebastian would
> not mind contributions.
Not at all!
--
Sebastian Schuberth
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vge
On 19.04.2014 15:35, Marat Radchenko wrote:
But in practice, msysgit is:
1) outdated msys that was patched in multiple ways without
sending patches upstream
It's not true that we are not sending patches upstream to MSYS, see [1].
It's just that most of them don't get included due to a la
On Sat, Apr 19, 2014 at 08:58:32PM +0400, Marat Radchenko wrote:
> On Sat, Apr 19, 2014 at 05:24:33PM +0200, Johannes Schindelin wrote:
> > Marat, please do not add to the confusion. "msysGit" is the name of the
> > *development environment* for developing Git for Windows.
>
> This confusion comes
On Sat, Apr 19, 2014 at 05:35:07PM +0400, Marat Radchenko wrote:
> > there are no 64 bit binaries shipped with msysgit is that nobody
> > needed them
>
> That's wrong. Google for 'windows x64 git' or 'msysgit x64'. People
> need it. There's even an issue [3] (stalled several years ago) in
> msysgi
Hi Marat,
On Sat, 19 Apr 2014, Marat Radchenko wrote:
> But in practice, msysgit is:
> 1) outdated msys that was patched in multiple ways without
> sending patches upstream
> 2) heavily patched git, again not upstreamed
Again, this time explicitly: I wish you had done a little more research
Am 19.04.2014 15:35, schrieb Marat Radchenko:
>> So the reason for this new package is that you need 64bit
>> binaries?
>
> That's the most important bit. Plus, weird ssh transfer speeds [1]
> caused by ansient openssh bundled in msysgit.
Yes the msysgit openssh is ancient and slow. Openssh in m
On Sat, Apr 19, 2014 at 05:24:33PM +0200, Johannes Schindelin wrote:
> Marat, please do not add to the confusion. "msysGit" is the name of the
> *development environment* for developing Git for Windows.
This confusion comes from the fact that major part of msysGit is packaged
with Git for Windows
Hi,
On Sat, 19 Apr 2014, Heiko Voigt wrote:
> On Thu, Apr 03, 2014 at 05:18:50PM +0400, ma...@slonopotamus.org wrote:
> > I'm proud to announce WinGit:
> > an attempt to bring Git powers to 64-bit Windows.
>
> So the reason for this new package is that you need 64bit binaries?
>
> > Relationshi
> So the reason for this new package is that you need 64bit binaries?
That's the most important bit. Plus, weird ssh transfer speeds [1] caused by
ansient openssh bundled in msysgit.
> I can see the need for a pure Windows solution (no msys tools at least for
> runtime).
Several Git scripts ar
Hi Marat,
On Thu, Apr 03, 2014 at 05:18:50PM +0400, ma...@slonopotamus.org wrote:
> I'm proud to announce WinGit:
> an attempt to bring Git powers to 64-bit Windows.
So the reason for this new package is that you need 64bit binaries?
> Relationship with msysgit
> =
>
> U
marat@ wrote:
> I'm proud to announce WinGit: an attempt to bring Git powers to 64-bit
> Windows.
>
> WinGit is currently used only by my coworkers and isn't considered
> production-ready-rock-solid. Use at your own risk.
Thank you for doing this, it's very much needed. It would be great if there
>
> I know that build.sh is UGLY, especially openssl part.
>
> Unlike msysgit, WinGit is a pure-Windows binary build with MSVC.
>
> Like msysgit, WinGit also uses msys environment (sh/perl/etc) both during
> build-time and runtime.
>
> WinGit adds a few patches to Git itself on top of msysgit ones.
On Thursday 03 April 2014 at 17:48:08 Konstantin Khomoutov wrote:
>
> What is the state of Unicode support in WinGit?
I haven't seen any Unicode-related issues when using through TortoiseGit.
Command-line usage is currently broken: no UTF-8 <->cmd.exe encoding
conversion is performed. Fixing thi
On Thu, 3 Apr 2014 17:18:50 +0400
ma...@slonopotamus.org wrote:
> I'm proud to announce WinGit:
> an attempt to bring Git powers to 64-bit Windows.
[...]
> Relationship with msysgit
> =
>
> Unlike msysgit, WinGit is a pure-Windows binary build with MSVC.
>
> Like msysgit,
I'm proud to announce WinGit:
an attempt to bring Git powers to 64-bit Windows.
WinGit is currently used only by my coworkers and isn't considered
production-ready-rock-solid. Use at your own risk.
Homepage & build instructions
-
https://github.com/slonopotamus/wingit
24 matches
Mail list logo
