git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: segfault in git-remote-http

From
Rrh <richard_hubbe11@lavabit.com>
Date
Apr 12, 2013, 15:20 UTC
Message-ID
<20130412082052.5afaa5cd88677eeb6da7daf0@lavabit.com>
In-Reply-To
<alpine.DEB.2.00.1304091924210.20932@tvnag.unkk.fr>

On Tue, 9 Apr 2013 19:25:53 +0200 (CEST) Daniel Stenberg <daniel@haxx.se> wrote:

Show 10 quoted lines
> On Tue, 9 Apr 2013, Jeff King wrote:
> 
> > git-remote-http does not touch the openssl code itself at all. We
> > only talk to curl, which handles all of the ssl (and may even be
> > built on gnutls). So if that is the problem, then I think it may be
> > a libcurl bug, not a git one.
> 
> ... and if/when you do make it a libcurl bug, please include more
> details that includes how to repeat the problem and what versions of
> libcurl and OpenSSL you're using.
I posted to web.curl.general few days ago....
Previous: Daniel StenbergNext: rh
Message 6 of 17 in “segfault in git-remote-http”
  1. rhApr 7, 2013
  2. rhApr 7, 2013
  3. rhApr 9, 2013
  4. Jeff KingApr 9, 2013
  5. Daniel StenbergApr 9, 2013
  6. rhApr 12, 2013
  7. rhApr 9, 2013
  8. Jeff KingApr 9, 2013
  9. rhApr 9, 2013
  10. Jeff KingApr 10, 2013
  11. rhApr 10, 2013
  12. Jeff KingApr 10, 2013
  13. Jeff KingApr 10, 2013
  14. rhApr 10, 2013
  15. rhApr 13, 2013
  16. rhApr 10, 2013
  17. Jeff KingApr 10, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.