git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: Sean <seanlkml@sympatico.ca>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Remove possible segfault in http-fetch.
Date: Sun, 21 May 2006 01:00:59 +0200	[thread overview]
Message-ID: <87ejyonvx0.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <BAYC1-PASMTP082397700A9527CC2F3786AEA40@CEZ.ICE> (Sean's message of "Sat, 20 May 2006 18:46:33 -0400")

* Sean:

> Testing seems to confirm that the segfault is removed by this patch.

It seems to fix it for me, too.

> As to why the website returns a 405 error in the first place is still
> a mystery to me.

The web server does not support PROPFIND.

  reply	other threads:[~2006-05-20 23:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-20 18:47 Segfaults with USE_CURL_MULTI Florian Weimer
     [not found] ` <20060520184633.76b438cc.seanlkml@sympatico.ca>
2006-05-20 22:46   ` [PATCH] Remove possible segfault in http-fetch Sean
2006-05-20 23:00     ` Florian Weimer [this message]
2006-05-21  7:49     ` Junio C Hamano
2006-05-31 16:07       ` Nick Hengeveld
2006-05-22 15:56 ` Segfaults with USE_CURL_MULTI Pavel Roskin

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=87ejyonvx0.fsf@mid.deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=git@vger.kernel.org \
    --cc=seanlkml@sympatico.ca \
    /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).