From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/28325] create new debuginfod.service.8 man page
Date: Sun, 31 Jul 2022 19:13:55 +0000 [thread overview]
Message-ID: <bug-28325-10460-KpX3eKzaIU@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28325-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28325
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
CC| |mark at klomp dot org
--- Comment #1 from Mark Wielaard <mark at klomp dot org> ---
commit 88c355011a78b5030fefedd10630bc99cecaceb6
Author: Noah Sanci <nsanci@redhat.com>
Date: Thu Jun 2 14:26:46 2022 -0400
Added debuginfod.service.8 manual page.
Signed-off-by: Noah Sanci <nsanci@redhat.com>
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2022-07-31 19:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 14:33 [Bug debuginfod/28325] New: " fche at redhat dot com
2022-05-27 15:09 ` [Bug debuginfod/28325] " nsanci at redhat dot com
2022-07-31 19:13 ` mark at klomp dot org [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-28325-10460-KpX3eKzaIU@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).