public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: "Frank Ch. Eigler" <fche@elastic.org>, elfutils-devel@sourceware.org
Subject: Re: PATCH PR30962, debuginfod
Date: Thu, 12 Oct 2023 17:25:01 +0200	[thread overview]
Message-ID: <f78aec611ca06525464e5efe449319b545910e9e.camel@klomp.org> (raw)
In-Reply-To: <20231011185758.GH8466@redhat.com>

Hi Frank,

On Wed, 2023-10-11 at 14:57 -0400, Frank Ch. Eigler wrote:
> > OK. But I think you should add an explanation or example to "Front-end
> > proxies can also elide sensitive path name components" paragraph. So
> > the user is fully aware what those "sensitive path names" are. Maybe
> > even add that debuginfod-find -v example so people can double check.
> 
> OK, rewrote the related text in the man page:

Looks really good and informative.

Thanks,

Mark

      reply	other threads:[~2023-10-12 15:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-10 20:37 Frank Ch. Eigler
2023-10-11 14:13 ` Mark Wielaard
2023-10-11 14:22   ` Frank Ch. Eigler
2023-10-11 14:50     ` Mark Wielaard
2023-10-11 18:57       ` Frank Ch. Eigler
2023-10-12 15:25         ` Mark Wielaard [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=f78aec611ca06525464e5efe449319b545910e9e.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=elfutils-devel@sourceware.org \
    --cc=fche@elastic.org \
    --cc=fche@redhat.com \
    /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).