archive mirror
 help / color / mirror / Atom feed
From: Davide Berardi <>
To: Jeff King <>
Cc: Junio C Hamano <>,
Subject: Re: [PATCH] Segmentation fault on non-commit objects.
Date: Thu, 31 Oct 2019 11:43:53 +0100	[thread overview]
Message-ID: <20191031104353.GA92289@carpenter.lan> (raw)
In-Reply-To: <>

>Davide, do you have an interest in trying to make these code paths a bit
>more robust?
Absolutely, I am writing a patch taking in consideration your comments.
I only need to write a test routine then I will commit my new patch.


Thanks and sorry for the silence but I am learning from your comments.

  reply	other threads:[~2019-10-31 10:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-29  9:27 [PATCH] Segmentation fault on non-commit objects Davide Berardi
2019-10-29 13:11 ` Johannes Schindelin
2019-11-01  0:26   ` Davide Berardi
2019-10-29 14:06 ` Jeff King
2019-10-30  2:44   ` Junio C Hamano
2019-10-31  5:37     ` Jeff King
2019-10-31 10:43       ` Davide Berardi [this message]
2019-11-01  0:29       ` Davide Berardi

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:

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

  git send-email \
    --in-reply-to=20191031104353.GA92289@carpenter.lan \ \ \ \ \

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