git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bob Copeland <me@bobcopeland.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: segfault in http-push
Date: Sun, 17 Feb 2008 21:05:55 -0500	[thread overview]
Message-ID: <20080218020555.GA12814@hash.localnet> (raw)
In-Reply-To: <alpine.LSU.1.00.0802172321551.30505@racer.site>

On Sun, Feb 17, 2008 at 11:23:38PM +0000, Johannes Schindelin wrote:
> I can only suspect that you mean 1.5.4.2, not 1.4.5.2 (which I could not 
> find).

Just so...

> Alas, a fix I provided for exactly this case did not make it into master 
> yet, let alone into any released version.  Can you please test the current 
> "next"?

Yep, next fixes it for me, thanks!

-- 
Bob Copeland %% www.bobcopeland.com 

  reply	other threads:[~2008-02-18  2:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-17 22:00 segfault in http-push Bob Copeland
2008-02-17 23:23 ` Johannes Schindelin
2008-02-18  2:05   ` Bob Copeland [this message]
2008-02-18  2:08     ` Johannes Schindelin
2008-02-18  3:06       ` 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=20080218020555.GA12814@hash.localnet \
    --to=me@bobcopeland.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).