From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/31620] debuginfod should not require ssl support from libcurl
Date: Mon, 15 Apr 2024 16:14:59 +0000 [thread overview]
Message-ID: <bug-31620-10460-Q2d5GJ9XDe@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31620-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31620
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|UNCONFIRMED |RESOLVED
--- Comment #11 from Frank Ch. Eigler <fche at redhat dot com> ---
commit 229aac471bb96035a4558db0dc74ff00d0aa08d1 (HEAD -> master, origin/main)
gpg: Signature made Mon 15 Apr 2024 11:49:43 AM EDT
gpg: using RSA key 4DD136490411C0A42B28844F258B6EFA0F209D24
gpg: Good signature from "Frank Ch. Eigler <fche@elastic.org>" [ultimate]
Author: Norbert Lange <nolange79@gmail.com>
Date: Fri Apr 12 22:03:08 2024 +0200
PR31620: debuginfod-client.c: Test for https support in libcurl
libcurl will fail if a protocol is requested that is not available.
Signed-off-by: Norbert Lange <nolange79@gmail.com>
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2024-04-15 16:15 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
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 [this message]
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-Q2d5GJ9XDe@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).