git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Cc: Alexey Spiridonov <snarkmaster@gmail.com>, git@vger.kernel.org
Subject: Re: "git am" crash (builtin/apply.c:2108) + small repro
Date: Fri, 12 Oct 2012 14:35:55 -0700	[thread overview]
Message-ID: <7vtxtz2x1g.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CACsJy8B4xeLSDPC42JifZwC7VWTPRd2iZfnxtPhf7u3OzOm_6Q@mail.gmail.com> (Nguyen Thai Ngoc Duy's message of "Sun, 7 Oct 2012 10:33:22 +0700")

Nguyen Thai Ngoc Duy <pclouds@gmail.com> writes:

> On Wed, Oct 3, 2012 at 10:44 PM, Alexey Spiridonov
> <snarkmaster@gmail.com> wrote:
>> Thanks a lot for trying this.
>>
>> My hashes match. I just re-reproduced it on two flavors of Linux (64
>> and 32-bit), with two different Git versions (see below). What
>> platform are you using?
>
> x86, 32 bit. Perhaps it has something to do with your configuration
> (config files, hooks, attributes). Assuming you use standard
> repository templates, you create new repo in your test so hooks and
> attributes are out. Is there anything suspicuous in "git config -l"?

I've never been a fan of update_pre_post_images().  I think I know
what is going on (--whitespace=fix).  Will post a fix sometime
later.

  reply	other threads:[~2012-10-12 21:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-01 18:33 "git am" crash (builtin/apply.c:2108) + small repro Alexey Spiridonov
2012-10-03 11:27 ` Nguyen Thai Ngoc Duy
2012-10-03 15:44   ` Alexey Spiridonov
2012-10-07  3:33     ` Nguyen Thai Ngoc Duy
2012-10-12 21:35       ` Junio C Hamano [this message]
     [not found]         ` <7vlifb2tfp.fsf@alter.siamese.dyndns.org>
2012-11-05 22:55           ` Alexey Spiridonov
2012-11-14 22:50             ` Junio C Hamano

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=7vtxtz2x1g.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=pclouds@gmail.com \
    --cc=snarkmaster@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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).