From: "Mike Pape" <dotzenlabs@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Marius Storm-Olsen" <marius@trolltech.com>,
"Dmitry Kakurin" <dmitry.kakurin@gmail.com>,
git@vger.kernel.org
Subject: Re: Git on MSys (or how to make it easy for Windows users to compile git)
Date: Fri, 3 Aug 2007 14:33:52 -0400 [thread overview]
Message-ID: <fd2562310708031133m72b43265n35277c360ef2ca7a@mail.gmail.com> (raw)
In-Reply-To: <46B36B7F.8010008@trolltech.com>
> >> 3) When "Setting up git" the second time, it feels like the whole thing
> >> is hanging; have let it run for ~5min now without anything happening.
> >> Not sure what's going on here. It looks like git.exe was ran with any
> >> options, but that should not consume 100% CPU.. Hmm
> >
> > Yep. I did not test the initial phase, and there is a serious bug in
> > setup_git_directory_gently() in origin/devel. I fixed that.
>
> Yup, work now.
Works for me as well now. One catch is that at work, I'm behind a
firewall so git:// doesn't work for me. I have a packaged version
that adds curl and expat, enables them in the build, and then falls
back to http:// if git:// fails in /etc/profile. Is that something
you'd want up on code.google.com?
next prev parent reply other threads:[~2007-08-03 18:33 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 21:23 Git on MSys (or how to make it easy for Windows users to compile git) Johannes Schindelin
2007-08-03 6:56 ` Dmitry Kakurin
2007-08-03 7:10 ` Marius Storm-Olsen
2007-08-03 9:58 ` Dmitry Kakurin
2007-08-03 11:43 ` Johannes Schindelin
2007-08-03 21:14 ` Dmitry Kakurin
2007-08-03 11:50 ` Johannes Schindelin
2007-08-03 12:47 ` Johannes Schindelin
2007-08-03 13:11 ` Marius Storm-Olsen
2007-08-03 13:37 ` Johannes Schindelin
2007-08-03 12:37 ` Johannes Schindelin
2007-08-03 13:08 ` Marius Storm-Olsen
2007-08-03 13:18 ` Johannes Schindelin
2007-08-03 13:24 ` Marius Storm-Olsen
2007-08-03 13:34 ` Johannes Schindelin
2007-08-03 15:34 ` Marius Storm-Olsen
2007-08-03 16:46 ` Johannes Schindelin
2007-08-03 17:53 ` Marius Storm-Olsen
2007-08-03 18:33 ` Mike Pape [this message]
2007-08-03 18:39 ` Marius Storm-Olsen
2007-08-03 18:55 ` Johannes Schindelin
2007-08-03 18:59 ` Marius Storm-Olsen
2007-08-03 19:13 ` Mike Pape
2007-08-03 19:18 ` Marius Storm-Olsen
2007-08-03 19:33 ` Johannes Schindelin
2007-08-03 21:21 ` Johannes Schindelin
2007-08-03 18:57 ` Johannes Schindelin
2007-08-03 21:21 ` Dmitry Kakurin
2007-08-03 21:32 ` Johannes Schindelin
2007-08-04 0:16 ` Torgil Svensson
2007-08-04 0:26 ` Johannes Schindelin
2007-08-05 23:41 ` Torgil Svensson
2007-08-06 0:11 ` Johannes Schindelin
2007-08-06 5:47 ` Marius Storm-Olsen
2007-08-06 10:24 ` Johannes Schindelin
2007-08-06 11:35 ` Marius Storm-Olsen
2007-08-09 8:47 ` Alex Riesen
2007-08-09 9:14 ` Johannes Schindelin
2007-08-09 13:55 ` Alex Riesen
2007-08-06 14:30 ` Torgil Svensson
2007-08-06 14:37 ` Johannes Schindelin
2007-08-03 7:12 ` Marius Storm-Olsen
2007-08-03 7:25 ` Marius Storm-Olsen
2007-08-03 11:17 ` Nguyen Thai Ngoc Duy
2007-08-03 11:29 ` Marius Storm-Olsen
2007-08-03 11:36 ` Nguyen Thai Ngoc Duy
2007-08-03 11:43 ` Marius Storm-Olsen
2007-08-03 12:14 ` Nguyen Thai Ngoc Duy
2007-08-03 12:32 ` Marius Storm-Olsen
2007-08-03 11:37 ` Johannes Schindelin
2007-08-03 11:48 ` Nguyen Thai Ngoc Duy
2007-08-03 11:59 ` Johannes Schindelin
2007-08-03 8:59 ` Matthieu Moy
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=fd2562310708031133m72b43265n35277c360ef2ca7a@mail.gmail.com \
--to=dotzenlabs@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=dmitry.kakurin@gmail.com \
--cc=git@vger.kernel.org \
--cc=marius@trolltech.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).