mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <>
To: Christoph Murczek <>
Subject: Re: AW: AW: "unable to remap" error with git svn after upgrade to Win10
Date: Wed, 15 Jul 2015 12:50:53 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Christoph,

On 2015-07-14 23:04, Christoph Murczek wrote:

> thanks for explaining why re-installing fixed my problem. Although I
> still can't wrap my head around why it happened in the first place. It
> could only be caused by Windows moving the base address of one, but
> not the other thus causing the overlap. Sounds weird. But then again,
> what do I know what's going on under the hoods when upgrading to
> Win10. ;)

To help that, I just wrote a wiki page about this very problem:

> In regards to your question: Yes I am running 64bit Windows, but the
> 32-bit version of git is the only thing I can download. I just
> double-checked on the webpage, but there's no option to get a 64 bit
> download link, and if there was some logic determining whether I
> should get 32 or 64 bit it puts me in the first bucket for some
> reason.
> I haven't considered building from source yet, mostly because the
> 32bit works fine so far. What would be the benefit? I guess
> performance when dealing with large repos? If you have a 64bit version
> available and need feedback let know. Always happy to help out :)

So I assumed that you found the official web site of Git for Windows 2.x:

Its download link leads to 32-bit/64-bit versions of the installer and the portable Git.


      reply	other threads:[~2015-07-15 10:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-13 12:24 AW: "unable to remap" error with git svn after upgrade to Win10 Christoph Murczek
2015-07-14  8:37 ` Johannes Schindelin
2015-07-14 21:04   ` AW: " Christoph Murczek
2015-07-15 10:50     ` Johannes Schindelin [this message]

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

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 read-only IMAP folder(s) and NNTP newsgroup(s).