From: Aaron Merey <amerey@redhat.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: elfutils-devel@sourceware.org
Subject: Re: [PATCH] Add man pages for some libelf functions
Date: Wed, 19 Jun 2024 13:25:45 -0400 [thread overview]
Message-ID: <CAJDtP-Rf53vOAEqua2xdBuKmtxDGv6Mi2WN7jB-jMZnPn6Wj6Q@mail.gmail.com> (raw)
In-Reply-To: <871q4tdj5p.fsf@redhat.com>
Hi Frank,
On Wed, Jun 19, 2024 at 11:52 AM Frank Ch. Eigler <fche@redhat.com> wrote:
>
> By the way, in addition or instead of using tarballs for carrying this
> bulk content toward review, a git branch holding it all work about as
> well.
I've created the branch users/amerey/manpages for holding this work.
It contains man pages for all libelf functions (ATM most of these man
pages consist of chatgpt raw output). I will update the branch as this
work progresses.
Aaron
next prev parent reply other threads:[~2024-06-19 17:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 20:01 Aaron Merey
2024-06-19 15:52 ` Frank Ch. Eigler
2024-06-19 17:25 ` Aaron Merey [this message]
2024-06-21 13:28 ` Mark Wielaard
2024-06-27 0:22 ` Aaron Merey
2024-06-28 11:36 ` Mark Wielaard
2024-06-28 18:35 ` Aaron Merey
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=CAJDtP-Rf53vOAEqua2xdBuKmtxDGv6Mi2WN7jB-jMZnPn6Wj6Q@mail.gmail.com \
--to=amerey@redhat.com \
--cc=elfutils-devel@sourceware.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).