git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <johannes.schindelin@gmx.de>
To: Gary England <GEngland@myvrx.com>
Cc: git@vger.kernel.org
Subject: Re: Bug report: Unhandled Exception
Date: Fri, 19 Jun 2015 16:19:42 +0200	[thread overview]
Message-ID: <35ee961018eec1fc84f4c3db16c5a9bb@www.dscho.org> (raw)
In-Reply-To: <DM2PR06MB4931E4534120B4A65580CA7D1A40@DM2PR06MB493.namprd06.prod.outlook.com>

Hi Gary,

On 2015-06-19 16:09, Gary England wrote:

> Will do. It's unlikely that I'll be able to reproduce the error. But,
> in the event that it happens again, I'll let you know.

For the record, the problem usually lies with a certain implementation detail on 32-bit only (if you know the `rebase.exe` tool -- confusingly completely unrelated to `git rebase`! -- you will know the root cause). That's why it is typically a sporadic problem only.

Ciao,
Johannes

      reply	other threads:[~2015-06-19 14:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-11 19:21 Bug report: Unhandled Exception Gary England
2015-06-19 12:58 ` Johannes Schindelin
2015-06-19 14:09   ` Gary England
2015-06-19 14:19     ` 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:
  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=35ee961018eec1fc84f4c3db16c5a9bb@www.dscho.org \
    --to=johannes.schindelin@gmx.de \
    --cc=GEngland@myvrx.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).