From: Roland McGrath <mcgrathr@google.com>
To: Mark Wielaard <mark@klomp.org>
Cc: Daniel Thornburgh <dthorn@google.com>, elfutils-devel@sourceware.org
Subject: Re: Local Build ID Directory Lookup (DEBUGINFOD_LOCAL_PATH)
Date: Wed, 14 Jun 2023 12:43:49 -0700 [thread overview]
Message-ID: <CAB=4xhosChLE02JHRF1SUS-=V7bf6eFU1665A=UKjxoGd9aBGA@mail.gmail.com> (raw)
In-Reply-To: <a600c48afae5040c821e3267f4d62c31d254d9c0.camel@klomp.org>
[-- Attachment #1: Type: text/plain, Size: 311 bytes --]
Personally I'm not concerned with any non-build-ID use cases any more. I
don't know if the rest of the world is OK with presuming that build
ID-based lookup is always the only thing you want nowadays. But it seems
plausible, since we rolled out Build ID in 2008 and it's been pretty
thoroughly adopted by now.
next prev parent reply other threads:[~2023-06-14 19:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 22:17 Daniel Thornburgh
2023-05-31 22:35 ` Paul Smith
2023-05-31 22:35 ` Frank Ch. Eigler
2023-05-31 22:45 ` Daniel Thornburgh
2023-05-31 23:04 ` Frank Ch. Eigler
2023-06-01 14:58 ` Frank Ch. Eigler
2023-06-01 20:54 ` Daniel Thornburgh
2023-06-01 21:21 ` Frank Ch. Eigler
2023-06-01 23:51 ` Daniel Thornburgh
2023-05-31 23:44 ` Roland McGrath
2023-06-14 15:57 ` Mark Wielaard
2023-06-14 19:43 ` Roland McGrath [this message]
2023-06-19 11:53 ` Mark Wielaard
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='CAB=4xhosChLE02JHRF1SUS-=V7bf6eFU1665A=UKjxoGd9aBGA@mail.gmail.com' \
--to=mcgrathr@google.com \
--cc=dthorn@google.com \
--cc=elfutils-devel@sourceware.org \
--cc=mark@klomp.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).