From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/29469] Add /buildid/BUILDID/header WEBAPI
Date: Thu, 11 Aug 2022 12:50:02 +0000 [thread overview]
Message-ID: <bug-29469-10460-ZH0HUQgJpD@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29469-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29469
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |DUPLICATE
Status|UNCONFIRMED |RESOLVED
--- Comment #4 from Frank Ch. Eigler <fche at redhat dot com> ---
this need has been identified in another RFE, with some work toward a webapi
and c api
*** This bug has been marked as a duplicate of bug 28284 ***
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2022-08-11 12:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 8:27 [Bug debuginfod/29469] New: " mliska at suse dot cz
2022-08-11 9:13 ` [Bug debuginfod/29469] " mark at klomp dot org
2022-08-11 9:17 ` mliska at suse dot cz
2022-08-11 9:49 ` mark at klomp dot org
2022-08-11 12:50 ` 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-29469-10460-ZH0HUQgJpD@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).