Vladimir Panteleev wrote:
On Fri, 20 May 2011 17:52:53 +0300, Don <nos...@nospam.com> wrote:
Vladimir Panteleev wrote:
On Fri, 20 May 2011 10:33:31 +0300, Don <nos...@nospam.com> wrote:
You've really got to be a fanboy to claim that git is supported on
Windows. Sure, it "works" -- in the same way that hammering a nail
with a rock "works".
You've mentioned some fairly untypical usage,
Huh????
You wouldn't consider using msysgit's bash shell and utilities on an AD
computer "untypical"?
I believe the typical usage of msysgit is:
1) Using the GUI utilities in combination with Git-Cheetah
2) Using git from the Windows command line via the git.cmd wrapper
so it's not surprising you ran into so many problems. Why would you
want to use the interactive bash shell?
Because it has slightly fewer bugs than the other alternatives.
Problems #6 and #7 on your list, maybe even #1 and #2 are msys problems.
They might not exist in, for example, cygwin.
fatal: index file corrupt
Words fail me...
Don't you think that a common data corruption problem would get a lot
more attention, given the number of Windows git users?
Yeah, I would have thought so. I wouldn't expect to find the root cause
first described as bug #21, yes TWENTY ONE in the msysgit database.
http://code.google.com/p/msysgit/issues/detail?id=21
---
"To my horror my first attempt at using git on the PC was a total
failure: since I was a cygwin guy I'd downloaded git for cygwin and
after finding that it failed on even the simplest init db I got the
comment from the lead developer that I should be using bin mode for my
file systems, and text mode mounts simply weren't 'the way to
emulate linux on windows' and there was no point in even thinking about
it! Aargh!
The cygwin git developer kindly hinted that there was a mingw/msys
version of git, and so I find myself here in this forum."
----
Can you describe a way for me to reproduce it? I'm genuinely curious.
I don't know exactly what causes it. It may have something to do with
the fact that I have a symlink in my path. Here's the result of a quick
google:
----
http://www.nishioka.com/blog/2008/01/source-control-with-git-and-cygwin.html
"If you use git on cygwin, you must be sure your disks are mounted
binmode or your database will get corrupted!
I had all my disks but one mounted binmode, but I also had a symbolic
link that ended up using that one textmode mount. This corrupted the
index and I got:
error: bad index file sha1 signature
fatal: index file corrupt"
Still not fixed in cygwin in 2011.
The only reason to use bash that I can think of is to allow
copy-pasting commands with parameters quoted/escaped in a way
incompatible to CMD. I'm not sure how vim fits the toolchain at all,
I think it's just provided as a bonus in msysgit. If you need a
proper *nix-like environment on Windows, have you looked at Cygwin?
For a long while, Cygwin was the only supported way to run git on
Windows.
Sorry, but your reply is a textbook example of fanboyism. On Windows,
git is an utterly lousy product. And yes, I have both cygwin and Msys.
Hm, are we pointing fingers now? :/
This is your post: "I tried X and it sucked! Therefore, anyone who says
that X doesn't suck MUST be a fanboy, number of world-wide happy X users
be damned."
"textbook example of fanboyism" seems to have become a textbook reply to
anyone trying to argue with a rant.
No, fanboyism is evidenced in dismissing a list of bugs. I think that
was a darn good list.
