From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/27950] New: separate common "debuginfod-client" docs into a new man page
Date: Thu, 03 Jun 2021 14:34:25 +0000 [thread overview]
Message-ID: <bug-27950-10460@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27950
Bug ID: 27950
Summary: separate common "debuginfod-client" docs into a new
man page
Product: elfutils
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: debuginfod
Assignee: unassigned at sourceware dot org
Reporter: fche at redhat dot com
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
The information common to client library operation (DEBUGINFOD_* environment
variables, cache control files, ...) is being replicated in three places in our
current man pages. We should make a new man page with just that info, and have
the other three refer to it. Or perhaps include it mechanically (at make
time?). Something to solve the manual replication efforts of this same
content.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-06-03 14:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 14:34 fche at redhat dot com [this message]
2021-07-07 18:59 ` [Bug debuginfod/27950] " alizhang at redhat dot com
2021-07-07 20:20 ` alizhang at redhat dot com
2021-08-11 22:30 ` fche at redhat 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-27950-10460@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).