From: "sergiodj at sergiodj dot net" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug gdb/27532] GDB should ask the user for permission before downloading debuginfod files
Date: Sun, 07 Mar 2021 20:41:04 +0000 [thread overview]
Message-ID: <bug-27532-10460-6GJwF430kb@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27532-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27532
Sergio Durigan Junior <sergiodj at sergiodj dot net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WONTFIX |---
Product|elfutils |gdb
Summary|debuginfod should ask the |GDB should ask the user for
|user for permission before |permission before
|downloading files |downloading debuginfod
| |files
Status|RESOLVED |REOPENED
Version|unspecified |HEAD
Component|debuginfod |gdb
--- Comment #4 from Sergio Durigan Junior <sergiodj at sergiodj dot net> ---
Instead of WONTFIX for debuginfod, I am reopening this against GDB because I
still think it is a good idea for the client to implement this feature.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-03-07 20:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-06 7:53 [Bug debuginfod/27532] New: debuginfod should ask the user for permission before downloading files sergiodj at sergiodj dot net
2021-03-06 11:30 ` [Bug debuginfod/27532] " fche at redhat dot com
2021-03-06 17:51 ` sergiodj at sergiodj dot net
2021-03-06 18:05 ` fche at redhat dot com
2021-03-07 20:41 ` sergiodj at sergiodj dot net [this message]
2021-11-24 0:32 ` [Bug gdb/27532] GDB should ask the user for permission before downloading debuginfod files amerey at redhat dot com
2021-11-24 3:51 ` sergiodj at sergiodj dot net
2022-01-09 16:36 ` hjl.tools at gmail 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-27532-10460-6GJwF430kb@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).