public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "nolange79 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/31620] debuginfod should not require ssl support from libcurl
Date: Fri, 12 Apr 2024 20:22:32 +0000	[thread overview]
Message-ID: <bug-31620-10460-1KW3pUD2CX@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31620-10460@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=31620

nolange79 at gmail dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #15454|0                           |1
        is obsolete|                            |

--- Comment #8 from nolange79 at gmail dot com ---
Created attachment 15462
  --> https://sourceware.org/bugzilla/attachment.cgi?id=15462&action=edit
Second version of the patch

This moves the check if https is supported into the function initializing
libcurl.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2024-04-12 20:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-08 16:20 [Bug debuginfod/31620] New: " nolange79 at gmail dot com
2024-04-08 16:30 ` [Bug debuginfod/31620] " fche at redhat dot com
2024-04-08 16:39 ` nolange79 at gmail dot com
2024-04-08 17:30 ` fche at redhat dot com
2024-04-09  7:32 ` nolange79 at gmail dot com
2024-04-09  7:35 ` nolange79 at gmail dot com
2024-04-11 22:03 ` fche at redhat dot com
2024-04-12 15:04 ` nolange79 at gmail dot com
2024-04-12 20:22 ` nolange79 at gmail dot com [this message]
2024-04-12 23:01 ` fche at redhat dot com
2024-04-14 14:41 ` nolange79 at gmail dot com
2024-04-15 16:14 ` fche at redhat dot com

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=bug-31620-10460-1KW3pUD2CX@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=elfutils-devel@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).