Re: Git-windows and git-svn?
On Nov 6, 2007, at 9:02 AM, Peter Karlsson wrote:
Show 7 quoted lines
> Steffen Prohaska:
>
>> Right. The experience should be good if you use binmode.
>
> Shouldn't it be possible to fix this by sprinkling the appropriate
> number of "b"s in the parameters to fopen()? Or is it more complicated
> than that?
It's more complicated. I tried. But others convinced me that it's harder than you think. The interfacing with other programs through shell scripts is one major problem. Another difficulty is that Cygwin's textmode is deprecated. So, the Cygwin guys won't help. Search the list archives for more details.
Show 8 quoted lines
>> But never use textmode. You'll not get an error right away. At first
>> git seems to work. But later it reports weird errors. The experience
>> is really bad. Don't do that.
>
> I got errors almost right away when trying that (I need text mode to
> interface with some other programs), so Cygwin-git is a no-go for
> me at
> the moment.
Same for me. You're welcome to join the msysgit effort ;)
But do not expect too much from my side. For me the only priority is to get the core git commands running. Everything that is needed to support a git-only workflow has top priority. Everything else has lowest priority. I'll refuse to put work into the scripts interfacing with other SCMs and I'll refuse to work on things needed to setup a git 'server', like git-shell.
> Of course, mixing msys-Git with Cygwin and ActiveState Perl
> is also an interesting experience, to say the least :-)
I can imagine that. If you already have some new insights how to handle such a situration it would be interesting if you could share some of them.
Steffen