git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Olsa <olsajiri@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [BUG] - git-read-tree segfaults
Date: Wed, 11 Mar 2009 08:59:06 +0100	[thread overview]
Message-ID: <35476bd20903110059v7d6d8aa0g93af17a940c91919@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0903102120290.14295@intel-tinevez-2-302>

On Tue, Mar 10, 2009 at 9:21 PM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> On Tue, 10 Mar 2009, Jiri Olsa wrote:
>
>> mb=$($GIT merge-base HEAD yyy)
>> $GIT read-tree $mb HEAD yyy
>
> While I agree that it is a bad thing for Git to segfault, I think this
> here is a pilot error.  You try to read 3 trees at the same time, but not
> perform a merge.  IMHO you want to add -m at least.

agreed, I've already said I executed it like this by an accident...
it was easy to recreate so I shared... I'm not saying it is a show stopper :)

jirka

>
> Ciao,
> Dscho
>
>

  reply	other threads:[~2009-03-11  8:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-10 19:34 [BUG] - git-read-tree segfaults Jiri Olsa
2009-03-10 19:50 ` Johannes Schindelin
2009-03-10 20:21 ` Johannes Schindelin
2009-03-11  7:59   ` Jiri Olsa [this message]
2009-03-11 12:04     ` Johannes Schindelin
2009-03-12  5:57       ` Junio C Hamano
2009-03-12  7:01         ` Junio C Hamano
2009-03-12  7:29           ` [PATCH] read-tree A B C: do not create a bogus index and do not segfault Junio C Hamano
2009-03-12 14:46             ` Daniel Barkalow
2009-03-12 16:34               ` Linus Torvalds
2009-03-14  6:41                 ` 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

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

  git send-email \
    --in-reply-to=35476bd20903110059v7d6d8aa0g93af17a940c91919@mail.gmail.com \
    --to=olsajiri@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --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).