From: Jon Seymour <jon.seymour@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: git on 64bit windows - state of the art?
Date: Tue, 19 Jun 2012 18:40:56 +1000 [thread overview]
Message-ID: <CAH3AnrrzKycCGprrWxiu5S5fuTHA8-cuNTi14Wz5WdtG+6FNJA@mail.gmail.com> (raw)
Hi,
I was wondering what the state of the art for running git on 64 bit Windows is?
I haven't tried it myself - my Windows VMs are 32bit - but colleagues
are reporting persistent problems with the cygwin build because of
(cygwin) rebasing issues [ the issue most often reveals itself as a
failure to fork subprocesses while executing git svn ]
We have tried to use cygwin's rebaseall to address the issue per the
advice on stackoverflow.com amongst other places, but this "solution"
doesn't seem to produce permanent results (even if the installed
cygwin code base remains stable). We tried msysgit to see if this
provided any relief, but it had similar issues (perhaps because cygwin
was also active at the time - I haven't had a chance to diagnose this
particular more thoroughly yet).
Has anyone got a recipe that provides a permanent and stable solution
to the (cygwin) 32/64bit rebasing issues?
jon.
next reply other threads:[~2012-06-19 8:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 8:40 Jon Seymour [this message]
2012-06-19 8:57 ` git on 64bit windows - state of the art? Erik Faye-Lund
2012-06-19 8:59 ` Philippe Vaucher
2012-06-19 9:10 ` Jon Seymour
2012-06-19 9:28 ` Philippe Vaucher
2012-06-19 9:49 ` Jon Seymour
2012-06-19 9:57 ` Jon Seymour
2012-06-19 11:02 ` Erik Faye-Lund
2012-06-19 19:16 ` Pascal Obry
2012-06-20 2:10 ` Jon Seymour
2012-06-20 6:57 ` Pascal Obry
[not found] ` <CAMSUDdYxveE=FUSvSOLowVPWh7F24UtVFJr8zyc0ANhm0La6zA@mail.gmail.com>
2012-06-21 2:22 ` Jon Seymour
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=CAH3AnrrzKycCGprrWxiu5S5fuTHA8-cuNTi14Wz5WdtG+6FNJA@mail.gmail.com \
--to=jon.seymour@gmail.com \
--cc=git@vger.kernel.org \
/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).